Re: BUG #13725: Logical Decoding - wrong results with large transactions and unfortunate timing - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #13725: Logical Decoding - wrong results with large transactions and unfortunate timing
Date
Msg-id 20151026113857.GC620@awork2.anarazel.de
Whole thread Raw
In response to Re: BUG #13725: Logical Decoding - wrong results with large transactions and unfortunate timing  ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>)
Responses Re: BUG #13725: Logical Decoding - wrong results with large transactions and unfortunate timing  ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>)
List pgsql-bugs
On 2015-10-26 12:34:48 +0100, Shulgin, Oleksandr wrote:
> On Mon, Oct 26, 2015 at 12:30 PM, Andres Freund <andres@anarazel.de> wrote:
>
> > On 2015-10-26 13:21:44 +0200, ofir.manor@gmail.com wrote:
> > > Yes, this is a small script to reproduce, the real code is Java, we saw
> > > sporadic wrong results.
> > > However, I'm interested in CDC (get change notifications per row to my
> > > app), not PG-to-PG replication.
> >
> > The streaming interface exists for row-by-row notification as well, and
> > is a *LOT* more efficient.
> >
>
> Yeah, but I don't think there's a workable Java implementation available
> yet?

No idea, but it's not that hard to write one.

> > If there's a bug here, we obviously need to fix it nonetheless.
> I would assume re-calculating end_of_wal in the while loop condition would
> fix this?

Why? That'd just lead to outputting more rows in one invocation, and
that's it? I think I'm not following what you see as the problem?

pgsql-bugs by date:

Previous
From: "Shulgin, Oleksandr"
Date:
Subject: Re: BUG #13725: Logical Decoding - wrong results with large transactions and unfortunate timing
Next
From: "Shulgin, Oleksandr"
Date:
Subject: Re: BUG #13725: Logical Decoding - wrong results with large transactions and unfortunate timing