Re: Recovery from WAL archives not advancing timeline?

On Mon, Aug 10, 2020 at 7:23 PM Rui DeSousa <rui(at)crazybean(dot)net> wrote:

>
>
> On Aug 10, 2020, at 8:03 PM, Rui DeSousa <rui(at)crazybean(dot)net> wrote:
>
>
>
> On Aug 10, 2020, at 4:28 PM, Don Seiler <don(at)seiler(dot)us> wrote:
>
> I'm following up to see if anyone else would categorize this as a bug. It
> renders my old primaries dead until I do a restore on them.
>
>
> No, I don’t think so. When you promote a standby; the primary will have
> to be restored or rewinded using pg_rewind to turn it into a replica.
> Another approach is to cleanly shutdown the primary and then you can turn
> it into a replica without doing a restore or pg_rewind.
>
>
> Just to be clear if it wasn’t already self evident by my above statement:
> The primary needs to be clearly shutdown (all WALs archived), apply all
> WALs to replica, promote the replica and then the original primary can be
> turn into a replica without a restore or pg_rewind.
>

But that was the process that I did. I cleanly shutdown the primary first.
The primary write one last WAL file as part of its shutdown. That WAL file
was archived and then restored and recovered on the replica. The replica
was them promoted.

This process was the same for both streaming and non-streaming replication.
However only the streaming replica wrote a .partial WAL file on promotion
(which was then archived and used by the former primary to start recovery).
The former primary doesn't even try to follow the timeline change in the
non-streaming scenario.

Don.

--
Don Seiler
www.seiler.us