Re: GUC parameter ACLs and physical walsender

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
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 17:56:19
Message-ID: 1387422.1781805379@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Davis <pgsql(at)j-davis(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next 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)
Previous Message Jeyaprakash Rajamani 2026-06-18 17:40:55 Re: Performance Degradation (Table becomes bloat) During Repeated Bulk UPDATE Operations