Re: PG16 walsender hangs in ResourceArrayEnlarge using pgoutput - Mailing list pgsql-bugs

From Amit Kapila
Subject Re: PG16 walsender hangs in ResourceArrayEnlarge using pgoutput
Date
Msg-id CAA4eK1JvHWm0s5xVe-WkvTvFhst5+wBQ4Zq0rasdDaDxXdOd9A@mail.gmail.com
Whole thread Raw
In response to RE: PG16 walsender hangs in ResourceArrayEnlarge using pgoutput  ("Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>)
List pgsql-bugs
On Thu, Jun 27, 2024 at 9:01 AM Zhijie Hou (Fujitsu)
<houzj.fnst@fujitsu.com> wrote:
>
> On Wednesday, June 26, 2024 1:25 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> > >
> > > IIUC, the relevant code was added in commit
> > > da324d6cd45bbbcc1682cc2fcbc4f575281916af. This is a PG16 commit, so
> > > how can the problem occur in PG15?
> > >
> >
> > I see that originally the slot allocation code was introduced in commit
> > 52e4f0cd472d39d07732b99559989ea3b615be78 but later the code refactored in
> > da324d6cd45bbbcc1682cc2fcbc4f575281916af. So, I agree that we must also
> > fix this in PG15.
>
> Thanks for confirming! Here are the patches for all branches.
>

Pushed.

--
With Regards,
Amit Kapila.



pgsql-bugs by date:

Previous
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: PG16 walsender hangs in ResourceArrayEnlarge using pgoutput
Next
From: Bertrand Drouvot
Date:
Subject: Re: error cache lookup failed in plpgsql function