Hi Brad,
We did some research on this at EDB and here is a summary of the finding
and suggested next steps.
*Context:*
*Given* a 3 node cluster M0, M1 and M2.
*And *M0 is the primary with M1 and M2 as the replicas - we will call
this *"T0"
(Timeline 0).*
*And* a *"switch over"* command is issued
Dilip Kumar wrote on 2020/11/15 04:47:12 AM:
> I am not sure how Patroni does it internally, can you explain the
> scenario in more detail? Suppose you are executing the promote on m-1
> and if the promotion is successful it will switch the timeline and it
> will create the timeline history file
On Thu, Nov 5, 2020 at 1:39 AM Brad Nicholson wrote:
>
> Hi,
>
> I've recently been seeing a race condition with the restore_command on
> replicas using streaming replication.
>
> On the primary, we are archiving wal files to s3 compatible storage via
> pgBackRest. In the recovery.conf section o
Hi,
I've recently been seeing a race condition with the restore_command on
replicas using streaming replication.
On the primary, we are archiving wal files to s3 compatible storage via
pgBackRest. In the recovery.conf section of the postgresql.conf file on the
replicas, we define the restore co
