From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Yoshinori Sano <yoshinori(dot)sano(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Simple, safe hot backup and recovery |
Date: | 2009-06-08 07:24:50 |
Message-ID: | 3f0b79eb0906080024w15523403q8c03eed1111503ef@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Sano-san,
On Fri, Jun 5, 2009 at 7:02 PM, Yoshinori Sano<yoshinori(dot)sano(at)gmail(dot)com> wrote:
>> In v8.4, pg_stop_backup waits until all WAL files used during backup
>> are archived.
>> So, "sleep" is already unnecessary for standalone hot backup.
>
> Oh, it's a great news! We don't need to use the unsafe approach (the
> sleep command) anymore if we use v8.4, do we?
Yes in upcoming v8.4. Of course, in or before v8.3, you still need to
make up the safe mechanism. For that, XLogArchiveIsBusy() function
which was added in v8.4 may be a good reference to you.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2009-06-08 07:34:28 | Re: pg_migrator issue with contrib |
Previous Message | Sebastien FLAESCH | 2009-06-08 07:20:29 | Re: INTERVAL SECOND limited to 59 seconds? |