From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_upgrade and rsync |
Date: | 2015-01-23 03:13:45 |
Message-ID: | 54C1BC69.4020605@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/22/15 10:05 PM, Stephen Frost wrote:
>> In addition, there is a possible race condition in rsync where a file
>> that is modified in the same second after rsync starts to copy will not
>> be picked up in a subsequent rsync unless --checksum is used. This is
>> fairly easy to prove and is shown here:
>>
>> https://github.com/pgmasters/backrest/blob/dev/test/lib/BackRestTest/BackupTest.pm#L1667
> Right, though that isn't really an issue in this specific case- we're
> talking about post-pg_upgrade but before the upgraded cluster has
> actually been started, so nothing should be modifying these files.
Indeed. This was really directed more at what Bruce said:
I am thinking the fix for standys would be similar to what we recommand
for upgrades with link mode using a rsync-created copy, e.g. use rsync
while the master is running to create a copy of the standby, then shut
down the master and run rsync again. However, at that point, you might
as well just take a base backup and be done with it.
--
- David Steele
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2015-01-23 03:42:45 | Re: Proposal: knowing detail of config files via SQL |
Previous Message | Stephen Frost | 2015-01-23 03:05:09 | Re: pg_upgrade and rsync |