Skip site navigation (1) Skip section navigation (2)

Re: Using pg_upgrade on log-shipping standby servers

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: 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-21 12:57:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sat, Jul 21, 2012 at 11:24:21AM +0300, Peter Eisentraut wrote:
> On fre, 2012-07-20 at 13:11 -0400, Bruce Momjian wrote:
> > I think the commands to run after pg_upgrade --link completes on both
> > primary and standby might be as easy as:
> > 
> >         cd /u/pg/pgsql.old/data
> >         find . -links 1 -exec cp {} /u/pgsql/data \;
> > 
> > Why would we want anything more complicated than this?
> In practice these are on different machines, and the way the machines
> are connected could vary wildly.  So an automated solution might be
> difficult to find.

Yeah, I was thinking of just suggesting scp as a doc example and let
users adjust that:

        cd /u/pg/pgsql.old/data
        find . -links 1 -exec scp {} postgres(at)momjian(dot)us:/u/pgsql/data \;

  Bruce Momjian  <bruce(at)momjian(dot)us>

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

In response to


pgsql-hackers by date

Next:From: Peter GeogheganDate: 2012-07-21 14:19:15
Subject: Re: 9.2 release schedule
Previous:From: Martijn van OosterhoutDate: 2012-07-21 08:55:57
Subject: Re: Resetting libpq connections after an app error

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group