Re: Recovery from WAL archives not advancing timeline?

From: Rui DeSousa <rui(at)crazybean(dot)net>
To: Don Seiler <don(at)seiler(dot)us>
Cc: Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Recovery from WAL archives not advancing timeline?
Date: 2020-08-11 00:23:53
Message-ID: 457D6CE0-90BE-4F88-87FB-A950F6C40AE5@crazybean.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> 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 <mailto: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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Mohammed Afsar 2020-08-11 00:31:25 Postgresql background writer and checkpointer memory utilization in Linux server
Previous Message Rui DeSousa 2020-08-11 00:03:54 Re: Recovery from WAL archives not advancing timeline?