Re: pg_upgrade and rsync - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: pg_upgrade and rsync
Date
Msg-id 54C19008.706@BlueTreble.com
Whole thread Raw
In response to Re: pg_upgrade and rsync  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade and rsync
List pgsql-hackers
On 1/22/15 5:43 PM, Bruce Momjian wrote:
> This brings up the other problem that the mod times of the files are
> likely to be different between master and slave --- should I recommend
> to only use rsync --checksum?

I don't think so. AIUI if the timestamps are different the very next thing it does is run the checksum (which is
expensive).So --checksum is just going to hurt.
 

> I am going to now conclude that rsync is never going to work for this,
> unless we have pg_upgrade preserve relfilenodes as well.  However, I am
> not even sure that is possible due to conflicts with system table
> relfilenodes created in the new cluster.

We've previously talked about required steps before an upgrade; perhaps we need a way to force an OID/relfilenode
changeon the old server prior to upgrade.
 

Or, thinking outside the box here... could this type of stuff be done in postgres itself so we could generate wal
that'sshipped to standby's? That would allow doing this as part of the formal upgrade process without the need for
preliminarysteps.
 
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: PATCH: Reducing lock strength of trigger and foreign key DDL
Next
From: Petr Jelinek
Date:
Subject: Re: TABLESAMPLE patch