RE: How can end users know the cause of LR slot sync delays?

From: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
Subject: RE: How can end users know the cause of LR slot sync delays?
Date: 2025-11-25 08:33:10
Message-ID: TY4PR01MB16907EF797D9B40A733982F6294D1A@TY4PR01MB16907.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tuesday, November 25, 2025 4:25 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Mon, Nov 24, 2025 at 11:24 AM shveta malik <shveta(dot)malik(at)gmail(dot)com>
> wrote:
> >
> > On Fri, Nov 21, 2025 at 6:21 PM Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>
> wrote:
> > >
> > > The Cbot complained that it was not able to build the docs. I have
> > > fixed it and attached the latest patch.
> > >
> >
> > Few comments on 001:
> >
>
> Fixed these and other open comments on 0001 and pushed. But I see a BF
> failure [1]. I think it is due to the reason that the patch forgot to release the
> slot in one of the code paths.

Right, I agree. Here is the patch to release the slot at necessary places.

Best Regards,
Hou zj

Attachment Content-Type Size
v1-0001-Fix-a-BF-failure-where-a-replication-slot-was-not.patch application/octet-stream 1.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2025-11-25 08:33:17 Re: ON CONFLICT DO SELECT (take 3)
Previous Message Amit Langote 2025-11-25 08:31:04 Re: generic plans and "initial" pruning