| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Oleksii Kliukin <alexk(at)hintbits(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: run pg_rewind on an uncleanly shut down cluster. |
| Date: | 2015-10-05 16:04:03 |
| Message-ID: | 20151005160403.GC6797@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 5, 2015 at 05:41:07PM +0200, Oleksii Kliukin wrote:
> Hello,
>
> I'm trying to find out how to rewind a cluster that was not shut down
> cleanly, in order to implement pg_rewind support in patroni (an
> automated failover system, https://github.com/zalando/patroni)
>
> At the moment, pg_rewind limits itself to only cleanly shut down
> clusters. This works nicely in the case of a split brain caused by the
> network partitioning. However, it doesn't cover the important case of a
> suddenly crashed master: the crashed cluster cannot be rewound to the
> new master.
Did you read this thread convering the same topic from a few weeks ago?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2015-10-05 16:23:08 | Re: Freeze avoidance of very large table. |
| Previous Message | Tom Lane | 2015-10-05 15:50:30 | Re: Less than ideal error reporting in pg_stat_statements |