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

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

On 2018-07-12 19:22:50 -0700, Christophe Pettus wrote:
> > 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.

Note that that message doesn't indicate a completed checkpoint, just
that one started. Do you see a "checkpoint complete: wrote ..." message
before the rewind started?


Andres Freund

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Kato, Sho 2018-07-13 02:58:53 How to make partitioning scale better for larger numbers of partitions
Previous Message Ideriha, Takeshi 2018-07-13 02:46:54 RE: ON CONFLICT DO NOTHING on pg_dump