RE: BUG #18055: logical decoding core on AllocateSnapshotBuilder() - Mailing list pgsql-bugs

From Zhijie Hou (Fujitsu)
Subject RE: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
Date
Msg-id OS0PR01MB5716DFC7D901742C5675471B94EEA@OS0PR01MB5716.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
List pgsql-bugs
On Tuesday, September 5, 2023 7:31 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> 
> On Fri, Aug 25, 2023 at 9:36 AM Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
> wrote:
> >
> > On Wednesday, August 23, 2023 4:47 PM Amit Kapila
> <amit.kapila16@gmail.com> wrote:
> > >
> > > On Mon, Aug 21, 2023 at 11:57 PM Andres Freund <andres@anarazel.de>
> > > wrote:
> > > >
> > > > -1. This makes things global concerns that shouldn't be.
> > > >
> > > > If we really need something to clean this up, I'd look at
> > > > MemoryContextRegisterResetCallback().
> > > >
> > >
> > > +1. This sounds like a better idea.
> >
> > Here is a small patch based on this idea.
> > I registered the callback under snapshot builder context and the
> > callback will reset the variables.
> >
> 
> LGTM. Unless Andres or Sawada-San thinks otherwise, I would like to proceed
> with this fix.

Thanks, attach the patches for all support branches. I have confirmed that they can
pass the regression test and fix the issue.

Best Regards,
Hou zj

Attachment

pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: BUG #18092: Unexpected Result by enable_seqscan
Next
From: PG Bug reporting form
Date:
Subject: BUG #18094: max max_connections cannot be set