Re: Logical decoding restart problems

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, konstantin knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
Subject: Re: Logical decoding restart problems
Date: 2016-08-31 00:28:21
Message-ID: CAMsr+YFTedOWkkdmJyQwfEYG9xybJ+4yi40x-Abm=Oa5rgisjw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 25 Aug. 2016 20:03, "Stas Kelvich" <s(dot)kelvich(at)postgrespro(dot)ru> wrote:
>
> > On 20 Aug 2016, at 15:59, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> >
> > I'll wait for a test case or some more detail.
>
> Thanks for clarification about how restart_lsn is working.
>
> Digging slightly deeper into this topic revealed that problem was in two
phase decoding, not it logical decoding itself.

Good to know. The behavior didn't make much sense for logical decoding but
bugs usually don't.

Do you plan to submit a patch for logical decoding of prepared transactions
to 10.0?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-08-31 00:53:44 Re: pageinspect: Hash index support
Previous Message Tom Lane 2016-08-30 22:47:42 Re: Missing checks when malloc returns NULL...