| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | dmitry(at)koterov(dot)ru |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Incomplete description of pg_start_backup? |
| Date: | 2013-05-14 14:05:40 |
| Message-ID: | CAMkU=1wShRyiysqoNOqEXrxDacJ9VzDGPRUfF2twRNX-iAwR4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 13, 2013 at 4:31 PM, Dmitry Koterov <dmitry(at)koterov(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2013-05-14 14:35:01 | Re: Parallel Sort |
| Previous Message | Benedikt Grundmann | 2013-05-14 13:48:55 | Re: streaming replication, "frozen snapshot backup on it" and missing relfile (postgres 9.2.3 on xfs + LVM) |