Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS
Date
Msg-id 54A9A7DF.1070406@dunslane.net
Whole thread Raw
In response to Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS
List pgsql-hackers
On 12/15/2014 12:04 PM, Andres Freund wrote:

>> I think the safest fix would be to defer catchup interrupt processing
>> while you're in this mode.  You don't really want to be processing any
>> remote sinval messages at all, I'd think.
> Well, we need to do relmap, smgr and similar things. So I think that'd
> be more complicated than we want.
>



Where are we on this? Traffic seems to have gone quite but we still have 
a bunch of buildfarm animals red.

cheers

andrew



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: addRangeTableEntry() relies on pstate, contrary to its documentation
Next
From: Andres Freund
Date:
Subject: Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS