| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'John R Pierce *EXTERN*'" <pierce(at)hogranch(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Online backup of PostgreSQL data. |
| Date: | 2015-09-17 08:15:34 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B50FA8266@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
John R Pierce wrote:
> to copy the data directory and have it be useful you need to bracket the copy with calls to
> pg_start_backup() and pg_stop_backup() .... this ensures the data files are coherent. this is in
> fact what pg_basebackup does for you....
I apologize for my fussiness, but this is a misconception I encounter so frequently
that I have to speak up.
The file system copy does not become consistent (isn't that what you meant?) if it
is surrounded by pg_start_backup() and pg_stop_backup(). What happens is that
a) a backup.label file is created that tells recovery where to start
b) more WAL is generated so that all changes can be replayed safely.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ramesh T | 2015-09-17 13:01:17 | Re: Import Problem |
| Previous Message | John R Pierce | 2015-09-17 07:53:33 | Re: Online backup of PostgreSQL data. |