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>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2026-06-18T17:37:06Z
Lists: pgsql-hackers

Attachments

On Fri, 2026-04-24 at 12:30 -0700, Jeff Davis wrote:
> 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.

Attached a rebased version, will commit soon. This will be a catalog
bump in beta2.

This fixes an issue introduced in a0ffa885e4, which was released in
v15. Unfortunately, we didn't find a reasonable back-patchable
solution, so I will commit only to master.

For backbranches, we could try to produce a better error message, but
that's about all we can do.

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.