Horton
Menu

Re: GUC parameter ACLs and physical walsender

Jeff Davis <pgsql@j-davis.com>

View thread
From: Jeff Davis <pgsql@j-davis.com>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: John Naylor <johncnaylorls@gmail.com>, pgsql-hackers@postgresql.org, Andrey Borodin <x4mmm@yandex-team.ru>
Date: 2026-04-24T19:30:09Z
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@j-davis.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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Nail pg_parameter_acl in relcache.

  2. catcache.c: use C_COLLATION_OID for texteqfast/texthashfast.