Re: Prevent restored WAL files from being archived again Re: Unnecessary WAL archiving after failover - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Prevent restored WAL files from being archived again Re: Unnecessary WAL archiving after failover
Date
Msg-id 50DF5BA7.6070200@vmware.com
Whole thread Raw
In response to Re: Prevent restored WAL files from being archived again Re: Unnecessary WAL archiving after failover  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Prevent restored WAL files from being archived again Re: Unnecessary WAL archiving after failover
List pgsql-hackers
On 02.10.2012 21:20, Fujii Masao wrote:
> On Wed, Oct 3, 2012 at 3:11 AM, Simon Riggs<simon@2ndquadrant.com>  wrote:
>> but its not high on my radar
>> right now unless you can explain why it should be higher.
>
> It may not be high, but I'm just worried that we are likely to forget to
> apply that change into HEAD if we postpone it furthermore.

Ping? I haven't been paying much attention to this, but please commit 
the 9.2 fix to HEAD. This just caused a small merge conflict when I 
tried to backport (or rather, forward-port) a patch. We do more changes 
to HEAD later.

- Heikki



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Timeline history files restored from archive not kept in pg_xlog, while WAL files are
Next
From: Pavel Stehule
Date:
Subject: Re: enhanced error fields