Re: pg_rewind fails after failover, 'invalid record length'

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Stuart Bishop <stuart(at)stuartbishop(dot)net>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pg_rewind fails after failover, 'invalid record length'
Date: 2017-02-16 02:58:19
Message-ID: CAB7nPqTUHwAOUqtuuz0agTgfcqYKhhCPUg9gFscCVrKF-__VEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Feb 15, 2017 at 7:02 PM, Stuart Bishop <stuart(at)stuartbishop(dot)net> wrote:
> I have a test case with 3 PostgreSQL 9.5.5 servers, one master and two
> hot standbys using standard streaming replication from the master.
> wal_log_hints is not enabled, but all systems initialized to use
> checksums.

The version of pg_rewind in Postgres 9.6 is able to handle timeline
switches, which allows far more flexibility, not the one of 9.5. If
the standby that has been promoted was the most advanced one, there is
actually no need to run pg_rewind on the second standby.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Антошин Антон Игоревич 2017-02-16 06:28:04 Found error in PostgreSQL 9.6.1 and 9.6.2 ...
Previous Message John McKown 2017-02-15 21:22:20 Re: BUG #14547: PgAdmin 4 browser pane has no horizontal scrolling