Re: GUC parameter ACLs and physical walsender

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, John Naylor <johncnaylorls(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Subject: Re: GUC parameter ACLs and physical walsender
Date: 2026-04-23 21:06:18
Message-ID: e23318a34c7ad2408dd9604ce441ba96110d557d.camel@j-davis.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2026-04-23 at 10:57 -0700, Mark Dilger wrote:
> John is right that the hardcoded BKI_ROWTYPE_OID(2173) makes this
> non-backportable as-is.

Right, but that leaves the questions:

(a) Is this the right fix for master?
(b) Is there anything we can do in the back branches, or we just leave
it as fix going forward only?

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2026-04-23 23:41:13 Re: GUC parameter ACLs and physical walsender
Previous Message Jacob Champion 2026-04-23 19:05:32 Re: oauth integer overflow