Thread: pg_rewind source-server connection
Hi all, May be it's time to document that source-server connection in pg_rewind must be non-replication and with superuser access. Consider this small patch for documentation. Previous discussion here: http://www.postgresql.org/message-id/54AEEC26.5030707@gmx.net ----- Pavel Luzanov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Attachment
On Wed, Nov 18, 2015 at 7:03 PM, Pavel Luzanov <p.luzanov@postgrespro.ru> wrote: > May be it's time to document that source-server connection in pg_rewind must > be non-replication and with superuser access. > Consider this small patch for documentation. +1. -- Michael
On 18.11.2015 14:29, Michael Paquier wrote: > On Wed, Nov 18, 2015 at 7:03 PM, Pavel Luzanov <p.luzanov@postgrespro.ru> wrote: >> May be it's time to document that source-server connection in pg_rewind must >> be non-replication and with superuser access. >> Consider this small patch for documentation. > +1. Just reminder, may be someone missed previous message. If this correction does not make sense, we can forget it. ----- Pavel Luzanov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
On Mon, Nov 23, 2015 at 9:46 PM, Pavel Luzanov <p.luzanov@postgrespro.ru> wrote:
On 18.11.2015 14:29, Michael Paquier wrote:On Wed, Nov 18, 2015 at 7:03 PM, Pavel Luzanov <p.luzanov@postgrespro.ru> wrote:Just reminder, may be someone missed previous message.May be it's time to document that source-server connection in pg_rewind must+1.
be non-replication and with superuser access.
Consider this small patch for documentation.
If this correction does not make sense, we can forget it.
I think it's useful and we should just commit it.
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs