aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2022-11-01 14:18:37 +0100
committerPeter Eisentraut <peter@eisentraut.org>2022-11-01 14:19:41 +0100
commit84387fc889442bd92b5969aa314b85cff360c7fe (patch)
tree7809b2c67c5c17f1452ce9359d6daf0cb65bad96
parent2ea5de296ef29d808e8cbc41f6053e33b7e7cf18 (diff)
downloadpostgresql-84387fc889442bd92b5969aa314b85cff360c7fe.tar.gz
postgresql-84387fc889442bd92b5969aa314b85cff360c7fe.zip
doc: Add note about lack of publication privileges
This gives some additional advice on using row filters and column lists on publications securely. Author: Antonin Houska <ah@cybertec.at> Reviewed-by: Euler Taveira <euler@eulerto.com> Discussion: https://www.postgresql.org/message-id/flat/20330.1652105397@antos
-rw-r--r--doc/src/sgml/logical-replication.sgml11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index e98538e5400..434bc311805 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -1571,6 +1571,17 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
</para>
<para>
+ There are currently no privileges on publications. Any subscription (that
+ is able to connect) can access any publication. Thus, if you intend to
+ hide some information from particular subscribers, such as by using row
+ filters or column lists, or by not adding the whole table to the
+ publication, be aware that other publications in the same database could
+ expose the same information. Publication privileges might be added to
+ <productname>PostgreSQL</productname> in the future to allow for
+ finer-grained access control.
+ </para>
+
+ <para>
To create a subscription, the user must be a superuser.
</para>