AW: AW: AW: AW: AW: AW: broken backup trail in case of quicklypatroni switchback and forth - Mailing list pgsql-general

From Zwettler Markus (OIZ)
Subject AW: AW: AW: AW: AW: AW: broken backup trail in case of quicklypatroni switchback and forth
Date
Msg-id c0bc128b5b584a379b3834f22a9c7664@zuerich.ch
Whole thread Raw
In response to Re: AW: AW: AW: AW: AW: broken backup trail in case of quickly patroniswitchback and forth  ("Brad Nicholson" <bradn@ca.ibm.com>)
Responses Re: AW: AW: AW: AW: AW: AW: broken backup trail in case of quicklypatroni switchback and forth  ("Brad Nicholson" <bradn@ca.ibm.com>)
List pgsql-general

How exactly? Please clarify.

 

 

"Zwettler Markus (OIZ)" <Markus.Zwettler@zuerich.ch> wrote on 2019/11/08 11:02:49 AM:

> From: "Zwettler Markus (OIZ)" <
Markus.Zwettler@zuerich.ch>
> To: Brad Nicholson <bradn@ca.ibm.com>
> Cc: Adrian Klaver <adrian.klaver@aklaver.com>, "pgsql-
>
general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
> Date: 2019/11/08 11:02 AM
> Subject: [EXTERNAL] AW:  AW:  AW: AW: AW: broken backup trail in
> case of quickly patroni switchback and forth

>
> Let me clarify: "But, it might start killing processes after a
> certain period if a _fast_ shutdown after SIGTERM didn't happen".

>  
> I am talking about stopping the Patroni master process with a systemd scipt.


Use the switchover functionality in Patroni first, and gate youur shutdown via systemd on the success of that operation.

Brad.

pgsql-general by date:

Previous
From: "Brad Nicholson"
Date:
Subject: Re: AW: AW: AW: AW: AW: broken backup trail in case of quickly patroniswitchback and forth
Next
From: "Brad Nicholson"
Date:
Subject: Re: AW: AW: AW: AW: AW: AW: broken backup trail in case of quicklypatroni switchback and forth