Re: Broken hint bits (freeze)

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Dmitriy Sarafannikov <dsarafannikov(at)yandex(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Borodin Vladimir <root(at)simply(dot)name>
Subject: Re: Broken hint bits (freeze)
Date: 2017-05-26 20:04:32
Message-ID: CAB7nPqQPMDQm9ZM59D6aw3K0NXxQ5FRi_7cqTHOF-11JM21iVw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 26, 2017 at 2:39 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Yeah, I think this is quite suspicious. This seems to indicate that
> not all WAL records are replicated before the switchover. What is the
> value of "synchronous_commit" you are using? I think you somehow need
> to ensure before switchover that all the WAL is replicated to ensure
> this is not a setup problem.

It is so easy to corrupt a server because of an incorrect base backup
flow or an incorrect switchover that it would be good first to
understand how you are doing your switchover. Any corruption happening
after a promotion, a failover or a switchover may be the top of the
iceberg of what's on the data pages, and you may just see one symptom
among other problems. Particularly, did you kill the master in any
violent way after promoting the standby? Has the former master been
able to perform at least once a clean shutdown checkpoint and has it
been rewound?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vladimir Borodin 2017-05-26 20:25:35 Re: Broken hint bits (freeze)
Previous Message Vik Fearing 2017-05-26 19:50:12 Re: Renaming a table to an array's autogenerated name