From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_standby -l might destory the archived file |
Date: | 2009-06-02 00:39:05 |
Message-ID: | 3f0b79eb0906011739i28361675q4e88c0648feb34e3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Mon, Jun 1, 2009 at 11:41 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
>> pg_standby can use ln command to restore an archived file,
>> which might destroy the archived file as follows.
>
> Does it matter? pg_standby's source area wouldn't normally be an
> "archive" in the real sense of the word, it's just a temporary staging
> area between master and slave.
If so, it might be deleted after triggering the warm-standby. But, we cannot
remove it because the latest xlog file which is required for normal recovery
might exist in it. This is another undesirable scenario. Is this problem?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-06-02 00:39:30 | Re: Patch: AdjustIntervalForTypmod shouldn't discard high-order data |
Previous Message | Kevin Grittner | 2009-06-02 00:13:05 | Re: User-facing aspects of serializable transactions |