From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Samrat Revagade <revagade(dot)samrat(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Speed up Switchover |
Date: | 2013-07-26 06:17:24 |
Message-ID: | CAB7nPqTRwGtNaBnZDVcmYDQsV7CKE7w9P5PJbt9t0kcDUud03Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jul 26, 2013 at 3:00 PM, Samrat Revagade
<revagade(dot)samrat(at)gmail(dot)com>wrote:
> > secondary without having to rsync the data as it can take up to 10 hours.
>
> pg_rewind (https://github.com/vmware/pg_rewind) is what you need.
>
> But I think it has a problem regarding the hint bits which Robert Hass
> pointed out.
> You can still solve hint bit problem by enabling new checksum feature, But
> you have to face consequences such as performance overhead.
>
> You can find the discussion about that on following link:
>
> http://www.postgresql.org/message-id/flat/CA+TgmoY4j+p7JY69ry8GpOSMMdZNYqU6dtiONPrcxaVG+SPByg(at)mail(dot)gmail(dot)com#CA+TgmoY4j+p7JY69ry8GpOSMMdZNYqU6dtiONPrcxaVG+SPByg@mail.gmail.com
>
Exactly, using checksums is mandatory or you could finish with corrupted
data after rewinding a data directory. Any help in testing or proposing
patches for pg_rewind is welcome. It is still in early development.
Thanks,
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Konoplev | 2013-07-26 06:22:18 | Re: Speed up Switchover |
Previous Message | Samrat Revagade | 2013-07-26 06:00:10 | Re: Speed up Switchover |