Re: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure
Date
Msg-id ZmD57ld6KIhJ4Pmi@paquier.xyz
Whole thread Raw
In response to RE: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure  (Floris Van Nee <florisvannee@Optiver.com>)
List pgsql-bugs
On Wed, Jun 05, 2024 at 10:24:43AM +0000, Floris Van Nee wrote:
> I noticed it but wasn't sure if it was necessary here due to the exceptional case here.
> It raises ereport error right after and can only reach this if the entry was created
> In the call to pgstat_prep_pending_entry before it, so it seems unlikely another
> backend holds a ref to it. I might be wrong though.

It does not prevent addressing the original issue, so pushed down to
15 after running concurrent tests for a few extra hours.

>> Attached is an updated patch with refined comments at the top of ?
>> pgstat_drop_entry(), to be applied to 15~.
>
> Thanks for testing the patch. Updated patch looks good to me.

I'll try to look at this one separately.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Erik Wienhold
Date:
Subject: Re: BUG #18495: invalid type mapping for timestamptz from call of: getMetaData and then geColumns on PgConnection.
Next
From: David Rowley
Date:
Subject: Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n