| From: | Antonin Houska <ah(at)cybertec(dot)at> |
|---|---|
| To: | "Euler Taveira" <euler(at)eulerto(dot)com> |
| Cc: | "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com>, "Peter Eisentraut" <peter(dot)eisentraut(at)enterprisedb(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Privileges on PUBLICATION |
| Date: | 2022-05-18 09:16:10 |
| Message-ID: | 55927.1652865370@antos |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Antonin Houska <ah(at)cybertec(dot)at> wrote:
> Euler Taveira <euler(at)eulerto(dot)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
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Draft-implementation-of-USAGE-privilege-on-PUBLICATI.patch | text/x-diff | 28.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-05-18 09:20:08 | Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set |
| Previous Message | Michael Paquier | 2022-05-18 09:02:00 | Re: Remove support for Visual Studio 2013 |