Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS
От | Andres Freund |
---|---|
Тема | Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS |
Дата | |
Msg-id | E8EAF9F8-13C0-42B6-99B9-84F6A7E1BC15@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Something is broken in logical decoding with
CLOBBER_CACHE_ALWAYS
|
Список | pgsql-hackers |
On January 4, 2015 9:51:43 PM CET, Andrew Dunstan <andrew@dunslane.net> wrote: > >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. I've a simple fix (similar too what I iriginally outkined) which I plan to post soonish. I've tried a bunch of things roughlyin the vein of Tom's suggestions, but they all are more invasive and still incomplete. Andres -- Please excuse brevity and formatting - I am writing this on my mobile phone. Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: