Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS
Date: 2015-01-04 20:51:43
Message-ID: 54A9A7DF.1070406@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-01-04 20:54:40 Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS
Previous Message Andres Freund 2015-01-04 18:12:40 Re: addRangeTableEntry() relies on pstate, contrary to its documentation