Re: Safe switchover - Mailing list pgsql-general

From Paul Förster
Subject Re: Safe switchover
Date
Msg-id 7E43945E-4571-4D30-9E8F-B940B9277DEF@gmail.com
Whole thread Raw
In response to Re: Safe switchover  (James Sewell <james.sewell@jirotech.com>)
Responses Re: Safe switchover
List pgsql-general
Hi James,

I wouldn't work out the procedure myself, especially since there is a free working solution already. It's dangerous if
youdo it yourself and make a mistake. 

In our company, we rely on Patroni (https://github.com/zalando/patroni). Yes, it uses pg_rewind in the background but
itdoes switchover and failover fast and reliably (also for high load databases), handles timelines automatically and so
on.

For the DCS, we use etcd, but you can choose yourself, which one you want.

Cheers,
Paul


> On 10. Jul, 2020, at 09:18, James Sewell <james.sewell@jirotech.com> wrote:
>
>
> - open connection to database
> - smart shutdown master
> - terminate all other connections
> - wait for shutdown (archiving will finish)
>
> OK despite what it looked like from the code - upon testing it seems like even a fast shutdown will wait for logs to
bearchived *as long as progress is being made* (the same as smart). 
>
>
> The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No
representationis made that this email is free of viruses or other defects. If you have received this communication in
error,you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the
senderof your incorrect receipt of this correspondence. 




pgsql-general by date:

Previous
From: James Sewell
Date:
Subject: Re: Safe switchover
Next
From: Paul Förster
Date:
Subject: Re: Postgresql Backup Encryption