AW: AW: AW: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth

How exactly? Please clarify.

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

> From: "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch<mailto:Markus(dot)Zwettler(at)zuerich(dot)ch>>
> To: Brad Nicholson <bradn(at)ca(dot)ibm(dot)com<mailto:bradn(at)ca(dot)ibm(dot)com>>
> Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com<mailto:adrian(dot)klaver(at)aklaver(dot)com>>, "pgsql-
> general(at)lists(dot)postgresql(dot)org<mailto:general(at)lists(dot)postgresql(dot)org>" <pgsql-general(at)lists(dot)postgresql(dot)org<mailto:pgsql-general(at)lists(dot)postgresql(dot)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.