| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Philippe Amelant *EXTERN*" <pamelant(at)companeo(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Understanding streaming replication |
| Date: | 2012-11-13 08:31:24 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C208AF068F@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Philippe Amelant wrote:
> I'm setting up a 3 nodes cluster and after some tests
> I just discover that the cascading slave does not recover.
Right, switching timeline over streaming replication
is not supported yet. There's a patch by Heikki in
the pipeline for this, so it will probably work in 9.3.
> As far as I can see in the 9.2 documentation it should work after
> an automatic reconnect to the new master.
Where did you see that?
> Is there any chance to get this fixed in 9.2.x ?
No. It is a new feature, and those aren't backpatched.
> In case of disaster on master and on standby, can I just restart the
> cascading slave
> after removing recovery.conf ?
The correct way it to "pg_ctl promote".
> Would it be better to copy all archives log from the master in pg_xlog
> on the third node
> and then restart it ?
> What is the best way to get back this node with minimal loss?
You can copy the archives, then wait until replication has
caught up, then promote the standby.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2012-11-13 08:40:27 | Re: Understanding streaming replication |
| Previous Message | Martijn van Oosterhout | 2012-11-13 07:12:40 | Re: integer instead of 'double precision'? |