Horton
Menu

Re: GUC parameter ACLs and physical walsender

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Mark Dilger <mark.dilger@enterprisedb.com>, John Naylor <johncnaylorls@gmail.com>, pgsql-hackers@postgresql.org, Andrey Borodin <x4mmm@yandex-team.ru>
Date: 2026-06-18T17:56:19Z
Lists: pgsql-hackers 
Jeff Davis <pgsql@j-davis.com> writes:
> 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.

It looks to me like the existing branches all assign OID 10097
to type pg_parameter_acl.  Could we get away with writing
BKI_ROWTYPE_OID(10097,ParameterAclRelation_Rowtype_Id)
in the back branches?  It'd depend on whether there are any
build options that change how many OIDs get assigned before
this one, but if there aren't ...

It might not be worth taking any risk for, though, given the
lack of field reports.

			regards, tom lane

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.