Re: pg_standby -l might destory the archived file

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_standby -l might destory the archived file
Date: 2009-06-02 01:00:43
Message-ID: 29796.1243904443@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> 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?

What recovery? In the problem case you're positing, the slave server
has executed a checkpoint and come up live. It's never going to be
interested in the old xlog again.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-06-02 01:09:54 Re: dblink patches for comment
Previous Message Tom Lane 2009-06-02 00:57:06 Re: Patch: AdjustIntervalForTypmod shouldn't discard high-order data