From: Antonin Houska <ah@cybertec.at>
To: Euler Taveira <euler@eulerto.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Privileges on PUBLICATION
Date: Wed, 18 May 2022 11:44:57 +0200
Message-ID: <57022.1652867097@antos> (raw)
In-Reply-To: <e6025f13-fefa-4ff2-9364-24f4c77fcf7a@www.fastmail.com>
References: <20330.1652105397@antos>
<8a00e0e1-dc4e-422c-9dcf-664b16b18625@www.fastmail.com>
<CAA4eK1Lya6BoMa1m8cTZrQ8KvABQpn3EsHDKRurz8UJeHsGnZw@mail.gmail.com>
<2810.1652171844@antos>
<d96103fe-99e2-4119-bd76-952d326b7539@www.fastmail.com>
<5859.1652423797@antos>
<e6025f13-fefa-4ff2-9364-24f4c77fcf7a@www.fastmail.com>
Euler Taveira <euler@eulerto.com> wrote:
> 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 thought it sound too negative if absence of some feature was mentioned
explicitly. However it makes sense to be clear from technical point of view.
> I also wouldn't use the warning tag because it fits in the same category as the
> other restrictions listed in the page.
ok, please see the next version.
--
Antonin Houska
Web: https://www.cybertec-postgresql.comAttachments:
[text/x-diff] publication_filtering_warning_v2.diff (1.1K, ../57022.1652867097@antos/2-publication_filtering_warning_v2.diff)
download | inline diff:diff --git a/doc/src/sgml/ref/create_publication.sgml b/doc/src/sgml/ref/create_publication.sgmlindex 1a828e8d2ff..259fe20a148 100644--- a/doc/src/sgml/ref/create_publication.sgml+++ b/doc/src/sgml/ref/create_publication.sgml@@ -112,6 +112,17 @@ CREATE PUBLICATION <replaceable class="parameter">name</replaceable>
Specifying a table that is part of a schema specified by
<literal>FOR ALL TABLES IN SCHEMA</literal> is not supported.
</para>
++ <para>+ Note that there are currently no privileges on publication, and that any+ subscriber can access any publication. Thus if you're trying to hide+ some information from particular subscribers (by using the+ <literal>WHERE</literal> clause or the column list, or by not adding the+ whole table to the publication), please be aware that other publications+ can expose the same information. Publication privileges might be added+ to <productname>PostgreSQL</productname> in the future to allow for+ fine-grained access control.+ </para>
</listitem>
</varlistentry>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: ah@cybertec.at, euler@eulerto.com, amit.kapila16@gmail.com, peter.eisentraut@enterprisedb.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Privileges on PUBLICATION
In-Reply-To: <57022.1652867097@antos>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox