Re: Using pg_upgrade on log-shipping standby servers - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Using pg_upgrade on log-shipping standby servers
Date
Msg-id 20120710161715.GA8689@momjian.us
Whole thread Raw
In response to Re: Using pg_upgrade on log-shipping standby servers  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Using pg_upgrade on log-shipping standby servers  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Tue, Jul 10, 2012 at 12:04:50PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > +    While a Log-Shipping Standby Server (<xref linkend="warm-standby">) can
> > +    be upgraded, the server must be in changed to a primary server to allow
> > +    writes, and after the upgrade it cannot be reused as a standby server.
> > +    (Running <command>rsync</> after the upgrade allows reuse.)
>
> "in changed"?  This sentence makes no sense at all to me.

Oops.  New wording attached with "in" removed:

    the server must be changed to a primary server

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Using pg_upgrade on log-shipping standby servers
Next
From: Magnus Hagander
Date:
Subject: Re: Using pg_upgrade on log-shipping standby servers