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: Tom Lane <tgl@sss.pgh.pa.us>
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-18T18:52:40Z
Lists: pgsql-hackers 
On Thu, 2026-06-18 at 13:56 -0400, Tom Lane wrote:
> 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 ...

Interesting idea.

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

That's what I was thinking. If someone is really stuck, there's an easy
workaround, just do a non-replication connection and "SELECT 1" first.

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.