Re: Pg stuck at 100% cpu, for multiple days

From: Joe Conway <mail(at)joeconway(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, depesz(at)depesz(dot)com, pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pg stuck at 100% cpu, for multiple days
Date: 2021-08-31 01:16:51
Message-ID: f57e21c1-11ef-b7ac-7df6-4dc2ade1ac2c@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/30/21 8:22 PM, Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2021-08-31 01:21:51 Re: replace IDENTIFY_SYSTEM code in receivelog.c with RunIdentifySystem()
Previous Message Tom Lane 2021-08-31 00:22:24 Re: Pg stuck at 100% cpu, for multiple days