From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | Patrick Dung <patrick_dkt(at)yahoo(dot)com(dot)hk>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: several questions about pg_dumpall, pg_start_backup, pg_basebackup and WAL |
Date: | 2013-08-27 19:31:35 |
Message-ID: | 1377631895.15061.YahooMailNeo@web162901.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Patrick Dung <patrick_dkt(at)yahoo(dot)com(dot)hk> wrote:
> Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
>> Patrick Dung wrote:
>>> It is possible that there is file changes (added or file size
>>> changed) between the pg_start_backup and pg_stop_backup.
>>
>> Yes.
>>
>>> Is the backup consistent?
>>
>> The tar or snapshot itself will not be consistent, it will have
>> to be recovered at least until the end on the online backup.
>
> I should ask: is the backup crash consistent?
PITR restore procedures will use the crash recovery mechanism to
make the database consistent, if that's what you mean.
> Which means it is consistent at the time that the pg_start_backup
> is run.
No. It will be consistent with the time that pg_stop_backup was
run, or any later point in time that you choose, as long as you
have WAL to that point in time.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Rene Romero Benavides | 2013-08-27 22:33:04 | 3 disks configured RAID 0 over 10 disks configured in RAID 5 (self replicating SAN) |
Previous Message | Dustin Wenz | 2013-08-27 16:25:10 | Re: Concurrent Users |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2013-08-27 19:35:40 | Re: pg_restore multiple --function options |
Previous Message | Alvaro Herrera | 2013-08-27 18:56:58 | Re: Properly initialize negative/empty cache entries in relfilenodemap |