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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:25:15
Message-ID: YS2E+0FeajNlpEQk@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 30, 2021 at 09:16:51PM -0400, Joe Conway wrote:
> On 8/30/21 8:22 PM, Tom Lane wrote:
>> 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 :-)

It looks something is messed up with the list of invalidation messages
to process in this code path. Maybe some incorrect memory context
handling?
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2021-08-31 01:31:18 Re: unpack_sql_state not called?
Previous Message Michael Paquier 2021-08-31 01:22:52 Re: perlcritic: prohibit map and grep in void conext