Re: GUC parameter ACLs and physical walsender
John Naylor <johncnaylorls@gmail.com>
From: John Naylor <johncnaylorls@gmail.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-hackers@postgresql.org, Andrey Borodin <x4mmm@yandex-team.ru>, Mark Dilger <mark.dilger@enterprisedb.com>
Date: 2026-04-23T03:27:15Z
Lists: pgsql-hackers
On Thu, Apr 23, 2026 at 2:19 AM Jeff Davis <pgsql@j-davis.com> wrote: > It seems to be because pg_parameter_acl is not nailed in cache. I > attached a quick patch to do so (which turns it into the "expected > permission denied" error). But I'm not sure if that's the right fix, or > if it would be a complete fix. I also don't think that would be > backportable, but perhaps? I think in existing installations AddNewRelationType() would have picked some oid already, so fixing rowtype_oid at initdb time would only work in the master branch. -- John Naylor Amazon Web Services
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Nail pg_parameter_acl in relcache.
- 4cc02b80774e 19 (unreleased) landed
-
catcache.c: use C_COLLATION_OID for texteqfast/texthashfast.
- dbf217c1c7c2 19 (unreleased) cited