Re: GUC parameter ACLs and physical walsender

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, 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-06-18 18:52:40
Message-ID: fccc0329cf4d7604b673076f9a72c43fcbc9d5c5.camel@j-davis.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2026-06-18 19:47:30 Re: proposal - queryid can be used as filter for auto_explain
Previous Message Lucas Jeffrey 2026-06-18 18:25:07 Re: [PATCH] Fix segmentation fault caused by reentrancy in RI_Fkey_cascade_del (ri_triggers.c)