Re: pg_start_backup does not actually allow for consistent, file-level backup

From: otheus uibk <otheus(dot)uibk(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_start_backup does not actually allow for consistent, file-level backup
Date: 2015-06-08 13:26:47
Message-ID: CALbQNd0gQnx1EEyJhXupnFFZ-AS5zbA3j_j_V1UDpT6cWwUiCw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 8, 2015 at 3:13 PM, otheus uibk <otheus(dot)uibk(at)gmail(dot)com> wrote:

> Thank you, all. The manual for 9.4 is indeed clearer on this point than
> the 9.1 version.
>

Just to nit-pick, I see nowhere in either version of the manual the
indication that it is normal for postgresql to continue to update files in
its data catalog between pg_start_backup and pg_stop_backup. The closest I
see comes in this paragraph:

** Some file system backup tools emit warnings or errors if the files they
are trying to copy change while the copy proceeds. When taking a base
backup of an active database, this situation is normal and not an error.

Does "this situation" refer to the tools emitting warnings or to the fact
that postgresql is updating the files? It might be the case, for instance,
that timestamps are updated but not the contents of the files (this is what
I had assumed prior to today).

--
Otheus
otheus(dot)uibk(at)gmail(dot)com
otheus(dot)shelling(at)uibk(dot)ac(dot)at

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-06-08 13:27:07 Re: pg_start_backup does not actually allow for consistent, file-level backup
Previous Message Andres Freund 2015-06-08 13:15:04 Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1