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 20120719160258.GB20583@momjian.us
Whole thread Raw
In response to Re: Using pg_upgrade on log-shipping standby servers  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Using pg_upgrade on log-shipping standby servers  (Robert Haas <robertmhaas@gmail.com>)
List 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@momjian.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@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Joel Jacobson
Date:
Subject: [PATCH] pg_dump: Sort overloaded functions in deterministic order
Next
From: Robert Haas
Date:
Subject: Re: [PERFORM] DELETE vs TRUNCATE explanation