From: Patrick Dung <patrick_dkt@yahoo.com.hk>
To: Kevin Grittner <kgrittn@ymail.com>
To: Albe Laurenz <laurenz.albe@wien.gv.at>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: several questions about pg_dumpall, pg_start_backup, pg_basebackup and WAL
Date: Sun, 1 Sep 2013 17:33:33 +0800 (SGT)
Message-ID: <1378028013.14431.YahooMailNeo@web193502.mail.sg3.yahoo.com> (raw)
In-Reply-To: <1377631895.15061.YahooMailNeo@web162901.mail.bf1.yahoo.com>
References: <1377186808.57546.YahooMailNeo@web193505.mail.sg3.yahoo.com>
<A737B7A37273E048B164557ADEF4A58B17C08086@ntex2010a.host.magwien.gv.at>
<1377494614.9111.YahooMailNeo@web193506.mail.sg3.yahoo.com>
<1377631895.15061.YahooMailNeo@web162901.mail.bf1.yahoo.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
'Crash consistent' is a term I heard in some oracle white papers..
If I am correct, it means the database would be consistent after the crash recovery is done.
>> 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.
In the manual, we where told to do three steps:
1) pg_start_backup
2) backup by tar
3) pg_stop_backup
If the backup is consistent when pg_stop_backup is called, I think it worth to mention it in the manual.
Thanks and regards,
Patrick Dung
________________________________
From: Kevin Grittner <kgrittn@ymail.com>
To: Patrick Dung <patrick_dkt@yahoo.com.hk>; Albe Laurenz <laurenz.albe@wien.gv.at>; "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Sent: Wednesday, August 28, 2013 3:31 AM
Subject: Re: [ADMIN] several questions about pg_dumpall, pg_start_backup, pg_basebackup and WAL
Patrick Dung <patrick_dkt@yahoo.com.hk> wrote:
> Albe Laurenz <laurenz.albe@wien.gv.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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: patrick_dkt@yahoo.com.hk, kgrittn@ymail.com, laurenz.albe@wien.gv.at
Subject: Re: several questions about pg_dumpall, pg_start_backup, pg_basebackup and WAL
In-Reply-To: <1378028013.14431.YahooMailNeo@web193502.mail.sg3.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox