Re: pg_upgrade and rsync

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

On 2015-01-23 14:27:51 -0500, Stephen Frost wrote:
> * Andres Freund (andres(at)2ndquadrant(dot)com) wrote:
> > On 2015-01-23 14:05:10 -0500, Stephen Frost wrote:
> > > If I follow what you're suggesting, pg_upgrade would
> > > need a new 'in-place' mode that removes all of the catalog tables from
> > > the old cluster and puts the new catalog tables into place and leaves
> > > everything else alone.
> >
> > No. Except that it'd preserve the relfilenodes (i.e. the filenames of
> > relations) it'd work exactly the same as today. The standby is simply
> > updated by rsyncing the new data directory of the primary to the
> > standby.
>
> 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.

> You'd still have to deal with the tablespace directories being renamed
> also, since we include the major version and catalog build in the
> directory name..

True.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-01-23 19:32:39 src/port/gethostname.c sure looks like dead code
Previous Message Stephen Frost 2015-01-23 19:27:51 Re: pg_upgrade and rsync