| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Updated backup APIs for non-exclusive backups |
| Date: | 2016-04-25 16:13:09 |
| Message-ID: | CACjxUsMuhecfrboyLnA=MWHbbqVvyBHzBr885Y1ARFq=W_iLzg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 25, 2016 at 9:11 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> PostgreSQL resource agent for Pacemaker removes backup_label in
> the case of failover to prevent the standby server from failing
> to recover from the crash.
Yikes! I hope that the providers of Pacemaker document that they
are using a technique which can silently corrupt the cluster.
http://tbeitr.blogspot.com/2015/07/deleting-backuplabel-on-restore-will.html
> This is not so neat solution, but they could live with the
> problem for a long time, so far.
It can work sometimes. It can also produce corruption which will
silently return incorrect results from queries for a long time
before some other symptom of the corruption surfaces.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-04-25 16:13:11 | Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE. |
| Previous Message | Robert Haas | 2016-04-25 16:04:22 | Re: Rename max_parallel_degree? |