Re: [BUG] Archive recovery failure on 9.3+. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [BUG] Archive recovery failure on 9.3+.
Date
Msg-id 16923.1389298576@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUG] Archive recovery failure on 9.3+.  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: [BUG] Archive recovery failure on 9.3+.
List pgsql-hackers
Heikki Linnakangas <hlinnakangas@vmware.com> writes:
> Actually, why is the partially-filled 000000010000000000000002 file 
> archived in the first place? ...

> So, the rationale is that otherwise it would take a long time until that 
> segment is archived. To be precise, I don't think the segment with the 
> old TLI would ever be archived without the above, but the same segment 
> on the new timeline would, after it fills up.

> Wouldn't it be better to not archive the old segment, and instead switch 
> to a new segment after writing the end-of-recovery checkpoint, so that 
> the segment on the new timeline is archived sooner?

Don't we want to archive both?  If you want to recover to the end of the
old timeline, you're going to need that file too, no?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [BUG] Archive recovery failure on 9.3+.
Next
From: knizhnik
Date:
Subject: Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL