Re: GUC parameter ACLs and physical walsender

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: John Naylor <johncnaylorls(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Subject: Re: GUC parameter ACLs and physical walsender
Date: 2026-04-24 19:30:09
Message-ID: 5d070cfb8f88337051691eeefc8983d003551be6.camel@j-davis.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2026-04-23 at 16:41 -0700, Mark Dilger wrote:
> On Thu, Apr 23, 2026 at 2:06 PM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> > (a) Is this the right fix for master?
>
> Yes.  This approach has no problem in master that I can see.
>  
> > (b) Is there anything we can do in the back branches, or we just
> > leave
> > it as fix going forward only?
>
> I don't see a solution.

OK. I'll wait a couple days to see if others have input on these two
points, and then I can commit this to master only. Ideally before
19beta1, because it would bump the catversion.

That would leave a bug in the back branches, but not a very serious one
as far as I can tell.

Regards,
Jeff Davis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2026-04-24 20:20:56 Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE
Previous Message Haibo Yan 2026-04-24 18:44:34 Re: Implement missing join selectivity estimation for range types