mirror of
https://github.com/postgres/postgres.git
synced 2025-12-19 17:02:53 +03:00
Make superuser imply replication privilege. The idea of a privilege that
superuser doesn't have doesn't make much sense, as a superuser can do whatever he wants through other means, anyway. So instead of granting replication privilege to superusers in CREATE USER time by default, allow replication connection from superusers whether or not they have the replication privilege. Patch by Noah Misch, per discussion on bug report #6264
This commit is contained in:
@@ -50,13 +50,13 @@ PostgreSQL documentation
|
||||
|
||||
<para>
|
||||
The transaction log is streamed over a regular
|
||||
<productname>PostgreSQL</productname> connection, and uses the
|
||||
replication protocol. The connection must be
|
||||
made with a user having <literal>REPLICATION</literal> permissions (see
|
||||
<xref linkend="role-attributes">), and the user must be granted explicit
|
||||
permissions in <filename>pg_hba.conf</filename>. The server must also
|
||||
be configured with <xref linkend="guc-max-wal-senders"> set high enough
|
||||
to leave at least one session available for the stream.
|
||||
<productname>PostgreSQL</productname> connection, and uses the replication
|
||||
protocol. The connection must be made with a superuser or a user
|
||||
having <literal>REPLICATION</literal> permissions (see
|
||||
<xref linkend="role-attributes">), and <filename>pg_hba.conf</filename>
|
||||
must explicitly permit the replication connection. The server must also be
|
||||
configured with <xref linkend="guc-max-wal-senders"> set high enough to
|
||||
leave at least one session available for the stream.
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user