From: | <fredrik(at)huitfeldt(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Streaming replication, master recycling |
Date: | 2016-05-11 04:31:14 |
Message-ID: | 1462941074281.128157.22300@webmail6 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi All,
we are currently using streaming replication on multiple node pairs. We are seeing some issues, but I am mainly interrested in clarification.
When a failover occurs, we touch the trigger file, promoting the previous slave to master. That works perfectly.
For recycling the previous master, we create a recovery.conf (with recovery_target_timeline = 'latest') and *try* to start up. If postgresql starts up, we accept it as a new slave. If it does not, we proceed with a full basebackup.
This approach seems to work, but I have found indications that it can lead to database corruption: <http://hlinnaka.iki.fi/presentations/NordicPGDay2015-pg_rewind.pdf>
I am mainly seeking understanding of if and why this approach is a bad idea.
Thanks,
Fredrik Huitfeldt
From | Date | Subject | |
---|---|---|---|
Next Message | Niels Kristian Schjødt | 2016-05-11 09:17:54 | Lightest way of checking if postgresql is running at the other end of an ssh tunnel? |
Previous Message | Sergey Konoplev | 2016-05-11 01:15:23 | Re: Increased I/O / Writes |