From: lejeczek <peljasz@yahoo.co.uk>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: highest timeline xxx of the primary is behind recovery timeline - backup of the underlying filesystem
Date: Tue, 19 Dec 2023 08:59:25 +0100
Message-ID: <5fd4f533-a8f8-41d6-a79a-2bcd14c5a273@yahoo.co.uk> (raw)
References: <5fd4f533-a8f8-41d6-a79a-2bcd14c5a273.ref@yahoo.co.uk>
Hi guys.
I see these every now and again:
2023-12-19 08:43:17.311 CET [2494773] FATAL: highest
timeline 105 of the primary is behind recovery timeline 106
and the only thing I can think is a backup which in my case
it a done with _libvirt_ as pgSQL cluster runs on Ubuntu VMs.
I'm not sure what exactly _virsh backup-begin_ does to the
qcow2 and as a consequence, to the the FS in the VMs, but..
it would be good to have those backups.
Any thoughts & ideas shared are much appreciated.
I guess my first question would be -- if such VM backup
might affect negatively pgSQL then, are there some tweaks,
ways to harden pgSQL cluster internally for such scenarios?
many thanks, L.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: peljasz@yahoo.co.uk, pgsql-admin@lists.postgresql.org
Subject: Re: highest timeline xxx of the primary is behind recovery timeline - backup of the underlying filesystem
In-Reply-To: <5fd4f533-a8f8-41d6-a79a-2bcd14c5a273@yahoo.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox