Re: Using pg_upgrade on log-shipping standby servers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Using pg_upgrade on log-shipping standby servers
Date: 2012-07-10 16:04:50
Message-ID: 22820.1341936290@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2012-07-10 16:17:15 Re: Using pg_upgrade on log-shipping standby servers
Previous Message Tom Lane 2012-07-10 16:02:48 Re: Re: Allow replacement of bloated primary key indexes without foreign key rebuilds