From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Sameer Thakur <samthakur74(at)gmail(dot)com>, Ants Aasma <ants(at)cybertec(dot)at>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, sthomas(at)optionshouse(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Samrat Revagade <revagade(dot)samrat(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com> |
Subject: | Re: Inconsistent DB data in Streaming Replication |
Date: | 2013-04-12 08:53:31 |
Message-ID: | 5167CB8B.5060402@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04/11/2013 07:29 PM, Fujii Masao wrote:
> On Thu, Apr 11, 2013 at 10:25 PM, Hannu Krosing <hannu(at)2ndquadrant(dot)com> wrote:
>> You just shut down the old master and let the standby catch
>> up (takas a few microseconds ;) ) before you promote it.
>>
>> After this you can start up the former master with recovery.conf
>> and it will follow nicely.
> No. When you shut down the old master, it might not have been
> able to send all the WAL records to the standby.
In what cases (other than a standby lagging too much or
not listening at all) have you observed this ?
> I have observed
> this situation several times. So in your approach, new standby
> might fail to catch up with the master nicely.
the page http://wiki.postgresql.org/wiki/Streaming_Replication claims this:
* Graceful shutdown
When smart/fast shutdown is requested, the primary waits to exit
until XLOG records have been sent to the standby, up to the
shutdown checkpoint record.
Maybe you were requesting immediate shutdown ?
Regards
Hannu Krosing
From | Date | Subject | |
---|---|---|---|
Next Message | Sameer Thakur | 2013-04-12 09:20:23 | Detach/attach table and index data files from one cluster to another |
Previous Message | Jeff Janes | 2013-04-12 06:14:10 | Re: (auto)vacuum truncate exclusive lock |