Re: Replication/cloning: rsync vs modification dates?

From: Michael Nolan <htfoot(at)gmail(dot)com>
To: Chris Angelico <rosuav(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Replication/cloning: rsync vs modification dates?
Date: 2012-07-16 15:58:57
Message-ID: CAOzAquJBMi-GnCAHf9Y6g2_K9TV00bvnA3dVMECHWS58tz0SdQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 7/16/12, Chris Angelico <rosuav(at)gmail(dot)com> wrote:
> On Tue, Jul 17, 2012 at 1:40 AM, Michael Nolan <htfoot(at)gmail(dot)com> wrote:
>> I did several weeks of tests on 9.1.3 using mod time and file size
>> rather than checksumming the files, that did not appear to cause any
>> problems
>> and it sped up the rsync considerably. (This was about a 40 GB
>> database.)
>
> Thanks! Is file size a necessary part of the check, or can mod time
> alone cover it?
>
> I'm looking at having my monitoring application automatically bring
> database nodes up, so it looks like the simplest way to handle it will
> be to have the new slave mandatorially do the backup/rsync, even if
> it's been down for only a couple of minutes. With a mod time check, I
> could hopefully do this without too much hassle.

As I understand the docs for rsync, it will use both mod time and file size
if told not to do checksums.
--
Mike Nolan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Angelico 2012-07-16 16:01:10 Re: Replication/cloning: rsync vs modification dates?
Previous Message Daniele Varrazzo 2012-07-16 15:57:02 Re: Can't figure out how to use now() in default for tsrange column (PG 9.2)