Re: requested timeline ... does not contain minimum recovery point ...

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: requested timeline ... does not contain minimum recovery point ...
Date: 2018-07-13 02:22:50
Message-ID: EC4D8830-7FB6-44D6-ACAA-8484BCD4F6BA@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> On Jul 12, 2018, at 17:52, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Wild guess: you did not issue a checkpoint on the promoted standby
> before running pg_rewind.

I don't believe a manual checkpoint was done on the target (promoted standby, new master), but it did one as usual during startup after the timeline switch:

> 2018-07-10 19:28:38 UTC [5068]: [1-1] user=,db=,app=,client= LOG: checkpoint starting: force

The pg_rewind was started about 90 seconds later.

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2018-07-13 02:28:01 Re: pg_create_logical_replication_slot returns text instead of name
Previous Message Michael Paquier 2018-07-13 02:22:11 Re: pg_create_logical_replication_slot returns text instead of name