| From: | "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: [Patch] Fix check_pub_rdt bypass when origin is set in same ALTER SUBSCRIPTION |
| Date: | 2026-06-02 02:13:57 |
| Message-ID: | TY4PR01MB1771889056A7ECBE5CF8CBFB394122@TY4PR01MB17718.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Saturday, May 30, 2026 6:19 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Tue, May 26, 2026 at 3:50 PM SATYANARAYANA NARLAPURAM
> <satyanarlapuram(at)gmail(dot)com> wrote:
> >
> > HI hackers,
> >
> > When ALTER SUBSCRIPTION SET (retain_dead_tuples = true, origin =
> > 'none') is used, the publisher version/recovery check was bypassed
> > because the origin handling unconditionally overwrote check_pub_rdt to
> false.
> >
> > Fix by using |= instead of = so that the flag set by
> > retain_dead_tuples cannot be cleared by a subsequent origin assignment in
> the same command.
Thanks for reporting ! I agree this needs to be fixed.
> >
>
> Thanks for catching this. Your fix LGTM. I won't be able to commit today as I
> have to travel. In the meantime, let's see if Hou-San or others have any
> comments.
The fix looks good to me as well.
Best Regards,
Hou zj
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2026-06-02 02:36:00 | Re: DOCS - missing SGML markup in some ALTER PUBLICATION examples |
| Previous Message | Mats Kindahl | 2026-06-02 02:13:45 | Re: pg_rewind does not rewind diverging timelines |