From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Release notes wording about logical replication as table owner |
Date: | 2023-09-06 19:36:28 |
Message-ID: | ZPjUvO8JuIrvvDZY@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 6, 2023 at 09:29:25PM +0200, Magnus Hagander wrote:
> We have:
>
> "This improves security and now requires subscription owners to be
> either superusers or to have SET ROLE permissions on all tables in the
> replication set. The previous behavior of performing all operations as
> the subscription owner can be enabled with the subscription
> run_as_owner option."
>
> How does one have SET ROLE permissions on a table? I think that's
> supposed to be:
>
> "subscription owners be either superusers or to have SET ROLE
> permissions on all roles owning tables in the replication set."
>
> Or something like that? Or can someone suggest a better wording?
You are exactly corrected. Patch attached and applied.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
Attachment | Content-Type | Size |
---|---|---|
role.diff | text/x-diff | 769 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2023-09-06 20:21:31 | Re: Eager page freeze criteria clarification |
Previous Message | Chris Cleveland | 2023-09-06 19:32:21 | Simple CustomScan example |