Re: Privileges on PUBLICATION
Antonin Houska <ah@cybertec.at>
From: Antonin Houska <ah@cybertec.at>
To: "Euler Taveira" <euler@eulerto.com>
Cc: "Amit Kapila" <amit.kapila16@gmail.com>,
"Peter Eisentraut" <peter.eisentraut@enterprisedb.com>,
"PostgreSQL Hackers" <pgsql-hackers@lists.postgresql.org>
Date: 2022-05-18T09:16:10Z
Lists: pgsql-hackers
Attachments
Antonin Houska <ah@cybertec.at> wrote: > Euler Taveira <euler@eulerto.com> wrote: > > > On Tue, May 10, 2022, at 5:37 AM, Antonin Houska wrote: > > > > My understanding is that the rows/columns filtering is a way for the > > *publisher* to control which data is available to particular replica. From > > this point of view, the publication privileges would just make the control > > complete. > > > > I agree. IMO it is a new feature. We already require high privilege for logical > > replication. Hence, we expect the replication user to have access to all data. > > Unfortunately, nobody mentioned about this requirement during the row filter / > > column list development; someone could have written a patch for GRANT ... ON > > PUBLICATION. > > I can try that for PG 16, unless someone is already working on it. The patch is attached to this message. -- Antonin Houska Web: https://www.cybertec-postgresql.com
Commits
-
Refactor ExecGrant_*() functions
- 369f09e420ef 16.0 cited
-
doc: Add note about lack of publication privileges
- 84387fc88944 16.0 landed