Postgres Pro
Downloads
Home   >   mailing lists

timeline problem when recovery - Mailing list pgsql-hackers

From Fabrice Chapuis
Subject timeline problem when recovery
Date
Msg-id CAA5-nLDV5jRF1HWnL9UT+C4KyQyYg9fvQi9+N1EcBa7jk1et-g@mail.gmail.com
Whole thread Raw
List pgsql-hackers
Tree view
Hi, I got this message on a standby after a FO of PG14 cluster with 3 nodes.

user=,db=,client=,application= LOG:  new timeline 20 forked off current database system timeline 19 before current recovery point CC8/164E9350

this message come from xlog.c rescanLatestTimeLine function:

if (currentTle->end < EndRecPtr)
{
ereport(LOG,
(errmsg("new timeline %u forked off current database system timeline %u before current recovery point %X/%X",
newtarget,
ThisTimeLineID,
LSN_FORMAT_ARGS(EndRecPtr))));
return false;
}

To complete recovery of standby, rewind was used to come back to the fork.
Is that means that standby by was before hand compare to the new primary (new TL)  and potentially loosing data on this primary.

Regards,

Fabrice

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Fix bank selection logic in SLRU
Next
From: Dilip Kumar
Date:
Subject: Re: Fix bank selection logic in SLRU