public inbox for [email protected]help / color / mirror / Atom feed
pg_rewind option clarification 5+ messages / 2 participants [nested] [flat]
* pg_rewind option clarification @ 2016-06-17 15:51 Bruce Momjian <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Bruce Momjian @ 2016-06-17 15:51 UTC (permalink / raw) To: pgsql-docs This patch clarifies the documentation for when --source-pgdata and --source-server can be used. I would like to apply this to 9.6. -- Bruce Momjian <[email protected]> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs Attachments: [text/x-diff] pg_rewind.diff (1.7K, 2-pg_rewind.diff) download | inline diff: diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml new file mode 100644 index afcc9b7..41bc4f2 *** a/doc/src/sgml/ref/pg_rewind.sgml --- b/doc/src/sgml/ref/pg_rewind.sgml *************** PostgreSQL documentation *** 122,129 **** <listitem> <para> Specifies path to the data directory of the source server, to ! synchronize the target with. When <option>--source-pgdata</> is ! used, the source server must be cleanly shut down. </para> </listitem> </varlistentry> --- 122,129 ---- <listitem> <para> Specifies path to the data directory of the source server, to ! synchronize the target with. This option requires the source server ! to be cleanly shut down. </para> </listitem> </varlistentry> *************** PostgreSQL documentation *** 135,142 **** Specifies a libpq connection string to connect to the source <productname>PostgreSQL</> server to synchronize the target with. The connection must be a normal (non-replication) connection ! with superuser access. The server must be up and running, ! and must not be in recovery mode. </para> </listitem> </varlistentry> --- 135,142 ---- Specifies a libpq connection string to connect to the source <productname>PostgreSQL</> server to synchronize the target with. The connection must be a normal (non-replication) connection ! with superuser access. This option requires the server to be running ! and not in recovery mode. </para> </listitem> </varlistentry> ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pg_rewind option clarification @ 2016-06-17 21:36 Michael Paquier <[email protected]> parent: Bruce Momjian <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Michael Paquier @ 2016-06-17 21:36 UTC (permalink / raw) To: Bruce Momjian <[email protected]>; +Cc: pgsql-docs On Sat, Jun 18, 2016 at 12:51 AM, Bruce Momjian <[email protected]> wrote: > This patch clarifies the documentation for when --source-pgdata and > --source-server can be used. > > I would like to apply this to 9.6. What's the difference between "up and running" and "running"? I thought that the current documentation was fine for this portion. -- Michael -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pg_rewind option clarification @ 2016-06-17 22:03 Bruce Momjian <[email protected]> parent: Michael Paquier <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Bruce Momjian @ 2016-06-17 22:03 UTC (permalink / raw) To: Michael Paquier <[email protected]>; +Cc: pgsql-docs On Sat, Jun 18, 2016 at 06:36:45AM +0900, Michael Paquier wrote: > On Sat, Jun 18, 2016 at 12:51 AM, Bruce Momjian <[email protected]> wrote: > > This patch clarifies the documentation for when --source-pgdata and > > --source-server can be used. > > > > I would like to apply this to 9.6. > > What's the difference between "up and running" and "running"? I > thought that the current documentation was fine for this portion. I don't know what the difference between "up" and "running" is, so I went with "running"; the original wording seemed to use two redundant terms. -- Bruce Momjian <[email protected]> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pg_rewind option clarification @ 2016-06-17 23:26 Michael Paquier <[email protected]> parent: Bruce Momjian <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Michael Paquier @ 2016-06-17 23:26 UTC (permalink / raw) To: Bruce Momjian <[email protected]>; +Cc: pgsql-docs On Sat, Jun 18, 2016 at 7:03 AM, Bruce Momjian <[email protected]> wrote: > On Sat, Jun 18, 2016 at 06:36:45AM +0900, Michael Paquier wrote: >> On Sat, Jun 18, 2016 at 12:51 AM, Bruce Momjian <[email protected]> wrote: >> > This patch clarifies the documentation for when --source-pgdata and >> > --source-server can be used. >> > >> > I would like to apply this to 9.6. >> >> What's the difference between "up and running" and "running"? I >> thought that the current documentation was fine for this portion. > > I don't know what the difference between "up" and "running" is, so I > went with "running"; the original wording seemed to use two redundant > terms. OK, no complains from here regarding this change then. -- Michael -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pg_rewind option clarification @ 2016-06-20 15:09 Bruce Momjian <[email protected]> parent: Michael Paquier <[email protected]> 0 siblings, 0 replies; 5+ messages in thread From: Bruce Momjian @ 2016-06-20 15:09 UTC (permalink / raw) To: Michael Paquier <[email protected]>; +Cc: pgsql-docs On Sat, Jun 18, 2016 at 08:26:30AM +0900, Michael Paquier wrote: > On Sat, Jun 18, 2016 at 7:03 AM, Bruce Momjian <[email protected]> wrote: > > On Sat, Jun 18, 2016 at 06:36:45AM +0900, Michael Paquier wrote: > >> On Sat, Jun 18, 2016 at 12:51 AM, Bruce Momjian <[email protected]> wrote: > >> > This patch clarifies the documentation for when --source-pgdata and > >> > --source-server can be used. > >> > > >> > I would like to apply this to 9.6. > >> > >> What's the difference between "up and running" and "running"? I > >> thought that the current documentation was fine for this portion. > > > > I don't know what the difference between "up" and "running" is, so I > > went with "running"; the original wording seemed to use two redundant > > terms. > > OK, no complains from here regarding this change then. Patch applied. -- Bruce Momjian <[email protected]> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2016-06-20 15:09 UTC | newest] Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2016-06-17 15:51 pg_rewind option clarification Bruce Momjian <[email protected]> 2016-06-17 21:36 ` Michael Paquier <[email protected]> 2016-06-17 22:03 ` Bruce Momjian <[email protected]> 2016-06-17 23:26 ` Michael Paquier <[email protected]> 2016-06-20 15:09 ` Bruce Momjian <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox