Re: Pg stuck at 100% cpu, for multiple days - Mailing list pgsql-hackers

From Joe Conway
Subject Re: Pg stuck at 100% cpu, for multiple days
Date
Msg-id f57e21c1-11ef-b7ac-7df6-4dc2ade1ac2c@joeconway.com
Whole thread Raw
In response to Re: Pg stuck at 100% cpu, for multiple days  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Pg stuck at 100% cpu, for multiple days
List pgsql-hackers
On 8/30/21 8:22 PM, Tom Lane wrote:
> Joe Conway <mail@joeconway.com> writes:
>> It would be interesting to step through a few times to see if it is 
>> really stuck in that loop.
> 
> Yeah, this single data point is not enough justification to blame
> dynahash.c (which is *extremely* battle-tested code, you'll recall).
> I'm inclined to guess that the looping is happening a few stack levels
> further up, in the logical-decoding code (which is, um, not so much).


Heh, fair point :-)

Joe

-- 
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Pg stuck at 100% cpu, for multiple days
Next
From: Michael Paquier
Date:
Subject: Re: replace IDENTIFY_SYSTEM code in receivelog.c with RunIdentifySystem()