From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: backup postgresql with snapshot AWS
Date: Fri, 19 Jan 2018 18:23:41 +0200
Message-ID: <ae8b9394-aabe-2dfa-70e1-b349100f90ee@matrix.gatewaynet.com> (raw)
In-Reply-To: <A6F69AB0-A8A3-4102-B11A-24868D7FD031@icloud.com>
References: <166191299.1443519.1516368751643@mail.virgilio.it>
<58e57feb-1a0a-bb44-55a6-5c94d294de9e@pgmasters.net>
<2ce36d42-c90a-ed10-173d-7b8445c1cec9@denninger.net>
<A6F69AB0-A8A3-4102-B11A-24868D7FD031@icloud.com>
On 19/01/2018 17:40, Rui DeSousa wrote:
> If the snapshot is not atomic and/or using multiple filesystems; that is fine as long as it’s issued and completed within the pg_start_backup() and pg_stop_backup() calls.
And as long as the needed wals belonging to that interval between start and stop are to be found in the archive when the problem arises. So the whole system must be well documented and periodically
tested.
>
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
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: achill@matrix.gatewaynet.com, pgsql-admin@lists.postgresql.org
Subject: Re: backup postgresql with snapshot AWS
In-Reply-To: <ae8b9394-aabe-2dfa-70e1-b349100f90ee@matrix.gatewaynet.com>
* 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