| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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:17:15 |
| Message-ID: | 20120710161715.GA8689@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 10, 2012 at 12:04:50PM -0400, Tom Lane wrote:
> 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.
Oops. New wording attached with "in" removed:
the server must be changed to a primary server
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| Attachment | Content-Type | Size |
|---|---|---|
| pg_upgrade.diff | text/x-diff | 830 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2012-07-10 16:21:35 | Re: Using pg_upgrade on log-shipping standby servers |
| Previous Message | Tom Lane | 2012-07-10 16:04:50 | Re: Using pg_upgrade on log-shipping standby servers |