From fa65c8c73cb21ab3154db2f0f291227ba901c996 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 11 Aug 2017 16:14:55 -0400 Subject: doc: Update description of rolreplication column Since PostgreSQL 9.6, rolreplication no longer determines whether a role can run pg_start_backup() and pg_stop_backup(), so remove that. Add that this attribute determines whether a role can create and drop replication slots. Reported-by: Fujii Masao --- doc/src/sgml/ref/create_role.sgml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/ref') diff --git a/doc/src/sgml/ref/create_role.sgml b/doc/src/sgml/ref/create_role.sgml index 4881e544391..36772b678a8 100644 --- a/doc/src/sgml/ref/create_role.sgml +++ b/doc/src/sgml/ref/create_role.sgml @@ -167,8 +167,11 @@ CREATE ROLE name [ [ WITH ] NOREPLICATION - These clauses determine whether a role is allowed to initiate - streaming replication or put the system in and out of backup mode. + These clauses determine whether a role is a replication role. A role + must have this attribute (or be a superuser) in order to be able to + connect to the server in replication mode (physical or logical + replication) and in order to be able to create or drop replication + slots. A role having the REPLICATION attribute is a very highly privileged role, and should only be used on roles actually used for replication. If not specified, -- cgit v1.2.3