Re: Using pg_upgrade on log-shipping standby servers

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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-19 16:02:58
Message-ID: 20120719160258.GB20583@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 19, 2012 at 09:41:29AM -0400, Robert Haas wrote:
> On Thu, Jul 19, 2012 at 2:38 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > No, the point is they run pg_upgrade on the stopped primary and stopped
> > standbys. Are those the same? I am not really sure.
>
> Of course not.

OK, but why? When the clusters are stopped they are the same, you are
running the same initdb on both matchines, and running the same
pg_upgrade. What would cause the difference, other than the Database
System Identifier, which we can deal with? I don't think we can
guarantee they are the same, but what would guarantee they are
different?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-07-19 16:17:12 Re: [PERFORM] DELETE vs TRUNCATE explanation
Previous Message Joel Jacobson 2012-07-19 15:47:35 [PATCH] pg_dump: Sort overloaded functions in deterministic order