Re: Fix logging for invalid recovery timeline - Mailing list pgsql-hackers

From Andrey M. Borodin
Subject Re: Fix logging for invalid recovery timeline
Date
Msg-id C748635E-B2FF-4813-B035-AE670832B9FD@yandex-team.ru
Whole thread Raw
Responses Re: Fix logging for invalid recovery timeline
List pgsql-hackers

> On 20 Dec 2024, at 20:37, David Steele <david@pgbackrest.org> wrote:
>
> "Latest checkpoint is at %X/%X on timeline %u, but in the history of the requested timeline, the server forked off
fromthat timeline at %X/%X." 

I think errdetai here is very hard to follow. I seem to understand what is going on after reading errmsg, but errdetai
makesme uncertain. 

If we call "tliSwitchPoint(CheckPointTLI, expectedTLEs, NULL);"
don't we risk to have again
ereport(ERROR,
(errmsg("requested timeline %u is not in this server's history",
tli)));
?

Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Discussion on a LISTEN-ALL syntax
Next
From: Vik Fearing
Date:
Subject: Re: Discussion on a LISTEN-ALL syntax