From 8df9bd0b445f9bd6134915d4417efde6e85e3add Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Mon, 13 Feb 2017 16:50:29 -0500 Subject: Change logical replication pg_hba.conf use Logical replication no longer uses the "replication" keyword. It just matches database entries in the normal way. The "replication" keyword now only applies to physical replication. Reviewed-by: Petr Jelinek --- doc/src/sgml/client-auth.sgml | 2 +- doc/src/sgml/logical-replication.sgml | 8 +++----- 2 files changed, 4 insertions(+), 6 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index bbd52a5418d..d6b8c04edc5 100644 --- a/doc/src/sgml/client-auth.sgml +++ b/doc/src/sgml/client-auth.sgml @@ -193,7 +193,7 @@ hostnossl database user members of the role, directly or indirectly, and not just by virtue of being a superuser. The value replication specifies that the record - matches if a replication connection is requested (note that + matches if a physical replication connection is requested (note that replication connections do not specify any particular database). Otherwise, this is the name of a specific PostgreSQL database. diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index a6c04e923da..6da39d25e38 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -295,11 +295,9 @@ Security - Logical replication connections occur in the same way as with physical streaming - replication. It requires access to be explicitly given using - pg_hba.conf. The role used for the replication - connection must have the REPLICATION attribute. This - gives a role access to both logical and physical replication. + The role used for the replication connection must have + the REPLICATION attribute. Access for the role must be + configured in pg_hba.conf. -- cgit v1.2.3