Re: Incomplete description of pg_start_backup? - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Incomplete description of pg_start_backup?
Date
Msg-id CAMkU=1wShRyiysqoNOqEXrxDacJ9VzDGPRUfF2twRNX-iAwR4Q@mail.gmail.com
Whole thread Raw
In response to Re: Incomplete description of pg_start_backup?  (Dmitry Koterov <dmitry@koterov.ru>)
Responses Re: Incomplete description of pg_start_backup?  (Dmitry Koterov <dmitry@koterov.ru>)
List pgsql-hackers
On Mon, May 13, 2013 at 4:31 PM, Dmitry Koterov <dmitry@koterov.ru> wrote:
Could you please provide a bit more detailed explanation on how it works? 

And how could postgres write at the middle of archiving files during an active pg_start_backup? if it could, here might be a case when a part of archived data file contains an overridden information "from the future",

The data files cannot contain information from the future.  If the backup is restored, it must be restored to the time of pg_stop_backup (at least), which means the data would at that point be from the past/present, not the future.

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Benedikt Grundmann
Date:
Subject: Re: streaming replication, "frozen snapshot backup on it" and missing relfile (postgres 9.2.3 on xfs + LVM)
Next
From: Noah Misch
Date:
Subject: Re: Parallel Sort