Re: Logical decoding restart problems - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Logical decoding restart problems
Date
Msg-id CAMsr+YFTedOWkkdmJyQwfEYG9xybJ+4yi40x-Abm=Oa5rgisjw@mail.gmail.com
Whole thread Raw
In response to Re: Logical decoding restart problems  (Stas Kelvich <s.kelvich@postgrespro.ru>)
Responses Re: Logical decoding restart problems  (Stas Kelvich <s.kelvich@postgrespro.ru>)
List pgsql-hackers
<p dir="ltr">On 25 Aug. 2016 20:03, "Stas Kelvich" <<a
href="mailto:s.kelvich@postgrespro.ru">s.kelvich@postgrespro.ru</a>>wrote:<br /> ><br /> > > On 20 Aug
2016,at 15:59, Craig Ringer <<a href="mailto:craig@2ndquadrant.com">craig@2ndquadrant.com</a>> wrote:<br /> >
><br/> > > I'll wait for a test case or some more detail.<br /> ><br /> > Thanks for clarification about
howrestart_lsn is working.<br /> ><br /> > Digging slightly deeper into this topic revealed that problem was in
twophase decoding, not it logical decoding itself.<p dir="ltr">Good to know. The behavior didn't make much sense for
logicaldecoding but bugs usually don't.<p dir="ltr">Do you plan to submit a patch for logical decoding of prepared
transactionsto 10.0? 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Missing checks when malloc returns NULL...
Next
From: Michael Paquier
Date:
Subject: Re: pageinspect: Hash index support