Re: pg_upgrade and rsync

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, 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-28 13:32:39
Message-ID: 20150128133239.GT3854@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce,

* Bruce Momjian (bruce(at)momjian(dot)us) wrote:
> On Tue, Jan 27, 2015 at 09:36:58AM -0500, Stephen Frost wrote:
> > The example listed works, but only when it's a local rsync:
> >
> > rsync --archive --hard-links --size-only old_dir new_dir remote_dir
> >
> > Perhaps a better example (or additional one) would be with a remote
> > rsync, including clarification of old and new dir, like so:
> >
> > (run in /var/lib/postgresql)
> > rsync --archive --hard-links --size-only \
> > 9.3/main \
> > 9.4/main \
> > server:/var/lib/postgresql/
> >
> > Note that 9.3/main and 9.4/main are two source directories for rsync to
> > copy over, while server:/var/lib/postgresql/ is a remote destination
> > directory. The above directories match a default Debian/Ubuntu install.
>
> OK, sorry everyone was confused by 'remote_dir'. Does this new patch
> help?

Looks better, but --links is not the same as --hard-links. The example
is right, the but documentation below it mentions "<option>--link</>"
which is for symlinks, not hard links.

This also should really include a discussion about dealing with
tablespaces, since the example command won't deal with them.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-01-28 14:03:01 Re: Parallel Seq Scan
Previous Message Stephen Frost 2015-01-28 13:25:45 Re: pg_upgrade and rsync