Re: Privileges on PUBLICATION

From: "Euler Taveira" <euler(at)eulerto(dot)com>
To: "Antonin Houska" <ah(at)cybertec(dot)at>
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-13 19:28:45
Message-ID: e6025f13-fefa-4ff2-9364-24f4c77fcf7a@www.fastmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 13, 2022, at 3:36 AM, Antonin Houska wrote:
> Attached is my proposal. It tries to be more specific and does not mention the
> absence of the privileges explicitly.
You explained the current issue but say nothing about the limitation. This
information will trigger a question possibly in one of the MLs. IMO if you say
something like the sentence above at the end, it will make it clear why that
setup expose all data (there is no access control to publications) and
explicitly say there is a TODO here.

Additional privileges might be added to control access to table data in a
future version of <productname>PostgreSQL</productname>.

I also wouldn't use the warning tag because it fits in the same category as the
other restrictions listed in the page.

--
Euler Taveira
EDB https://www.enterprisedb.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2022-05-13 19:29:53 Re: Item compression in the Gist index
Previous Message Bruce Momjian 2022-05-13 19:02:45 Re: Multi-Master Logical Replication