| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Michael Paquier *EXTERN*" <michael(dot)paquier(at)gmail(dot)com>, James Sewell <james(dot)sewell(at)lisasoft(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Failback without rebuild |
| Date: | 2014-02-07 07:41:26 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17CA3B08@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier wrote:
> On Fri, Feb 7, 2014 at 3:02 PM, James Sewell <james(dot)sewell(at)lisasoft(dot)com> wrote:
>
>> Node A could get ahead even if it has been shut down cleanly BEFORE the promotion?
>> I'd always assumed if I shut down the master the slave would be at the same point after shutdown
>> - is this incorrect?
>
> Yes and no. A node will wait at shutdown until all the *connected* slaves have flushed necessary WALs
> to disk. But if the slave is not connected at the moment of shutdown, it might not be the case.
Even if the slave is connected, there was a bug:
http://www.postgresql.org/message-id/E1UrWwA-0004LR-D2@gemulon.postgresql.org
So you need at least 9.3.0, 9.2.5 or 9.1.10 for this to work properly.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-02-07 08:26:21 | Re: Typo in a comment? |
| Previous Message | Michael Paquier | 2014-02-07 07:24:49 | Re: PostgreSQL Failback without rebuild |