Re: AW: broken backup trail in case of quickly patroni switchback andforth - Mailing list pgsql-general

From Adrian Klaver
Subject Re: AW: broken backup trail in case of quickly patroni switchback andforth
Date
Msg-id 26aad343-c08d-d53d-9788-c592450ce438@aklaver.com
Whole thread Raw
In response to AW: broken backup trail in case of quickly patroni switchback andforth  ("Zwettler Markus (OIZ)" <Markus.Zwettler@zuerich.ch>)
Responses AW: AW: broken backup trail in case of quickly patroni switchback andforth
List pgsql-general
On 11/7/19 7:18 AM, Zwettler Markus (OIZ) wrote:
> I already asked the Patroni folks. They told me this is not related to Patroni but Postgresql. ;-)

Hard to say without more information:

1) Postgres version

2) Setup/config info

3) Detail if what happened between 12:00 and 12:10

> 
> - Markus
> 
> 
> 
> On 11/7/19 5:52 AM, Zwettler Markus (OIZ) wrote:
>> we are using Patroni for management of our Postgres standby databases.
>>
>> we take our (wal) backups on the primary side based on intervals and thresholds.
>> our archived wal's are written to a local wal directory first and moved to tape afterwards.
>>
>> we got a case where Patroni switched back and forth sides quickly, e.g.:
>> 12:00h: primary - standby
>> 12:05h: standby - primary
>> 12:10h: primary - standby
>>
>> we realised that we will not have a wal backup of those wal's generated between 12:05h and 12:10h in this scenario.
>>
>> how can we make sure that the whole wal sequence trail will be backuped? any idea?
> 
> Probably best to ask the Patroni folks:
> 
> https://github.com/zalando/patroni#community
> 
>>
>> - Markus
>>
>>
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: "Zwettler Markus (OIZ)"
Date:
Subject: AW: broken backup trail in case of quickly patroni switchback andforth
Next
From: stan
Date:
Subject: 11 -> 12 upgrade on Debian Ubuntu