| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Using pg_upgrade on log-shipping standby servers |
| Date: | 2012-07-26 17:24:19 |
| Message-ID: | CA+TgmoaRVjx==hc7w4rfwt9z+2RgOhWN-2xSKdHm9k273BLSFw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 26, 2012 at 12:06 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I don't see the "don't modify the user files" behavior changing anytime
> soon, and it is documented, so I feel pretty confident that those files
> were not modified on the primary or standby cluster, and are hence the
> same, or at least as "the same" as they were when they were running the
> older major version of Postgres.
>
> Is that sufficient?
Well, at the very least, you need to guarantee that the standby is
caught up - i.e. that it replayed all the WAL records that were
generated on the master before it was shut down for the final time. I
don't think that telling the user that they must be sure to do that is
sufficient - you need some kind of built-in safeguard that will
complain loudly if it's not the case.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-07-26 17:37:37 | Re: Covering Indexes |
| Previous Message | Robert Haas | 2012-07-26 17:17:55 | Re: Covering Indexes |