Re: pg_upgrade and rsync

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: pg_upgrade and rsync
Date: 2015-01-25 03:04:01
Message-ID: 20150125030401.GA30465@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 23, 2015 at 02:34:36PM -0500, Stephen Frost wrote:
> > > You'd have to replace the existing data directory on the master to do
> > > that, which pg_upgrade was designed specifically to not do, in case
> > > things went poorly.
> >
> > Why? Just rsync the new data directory onto the old directory on the
> > standbys. That's fine and simple.
>
> That still doesn't address the need to use --size-only, it would just
> mean that you don't need to use -H. If anything the -H part is the
> aspect which worries me the least about this approach.

I can now confirm that it works, just as Stephen said. I was able to
upgrade a standby cluster that contained the regression database, and
the pg_dump output was perfect.

I am attaching doc instruction that I will add to all branches as soon
as someone else confirms my results. You will need to use rsync
--itemize-changes to see the hard links being created, e.g.:

hf+++++++++ pgsql/data/base/16415/28188 => pgsql.old/data/base/16384/28188

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

+ Everyone has their own god. +

Attachment Content-Type Size
rsync.diff text/x-diff 3.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2015-01-25 08:59:33 Re: New CF app deployment
Previous Message Peter Geoghegan 2015-01-25 02:37:18 Re: Abbreviated keys for Datum tuplesort (was: Re: B-Tree support function number 3 (strxfrm() optimization))