From: | David Greco <David_Greco(at)harte-hanks(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Streaming Replication 9.2 |
Date: | 2013-04-11 14:51:37 |
Message-ID: | 187F6C10D2931A4386EE8E58E13857F6303AC41F@BY2PRD0811MB415.namprd08.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I've setup streaming replication between two 9.2 servers, and have a few concerns/questions. I set it up with a very large wal_keep_segments, 17000, and do NOT ship the logs to the standby.
When I failover to the slave, MUST the process for bringing back up the former master initially as a slave involve copying a base backup from the new master back to the former master? Even if I am keeping enough wal segments to include all changes since the former slave was promoted? I tried just bringing up the former master as a slave but it complains "timeline 2 of the primary does not match recovery target timeline 1".
If this is true, what is a good strategy for handling primary/slave in distant geographic locations where copying a base backup between the two is not terribly convenient?
From | Date | Subject | |
---|---|---|---|
Next Message | ledwabakg | 2013-04-11 15:06:01 | Re: UPDATE .. JOIN? |
Previous Message | Matthew Churcher | 2013-04-11 14:40:32 | Cost of initiating cursors |