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
rolreplication
bool
- Role is a replication role. That is, this role can initiate streaming
- replication (see ) and set/unset
- the system backup mode using pg_start_backup> and
- pg_stop_backup>
+ Role is a replication role. A replication role can initiate replication
+ connections and create and drop replication slots.
bool
- Role is a replication role. That is, this role can initiate streaming
- replication (see ) and set/unset
- the system backup mode using pg_start_backup> and
- pg_stop_backup>
+ Role is a replication role. A replication role can initiate replication
+ connections and create and drop replication slots.
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,