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

From: Andres Freund <andres(at)anarazel(dot)de>
To: "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>
Cc: Ofir Manor <ofir(dot)manor(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13725: Logical Decoding - wrong results with large transactions and unfortunate timing
Date: 2015-10-26 11:38:57
Message-ID: 20151026113857.GC620@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)anarazel(dot)de> wrote:
>
> > On 2015-10-26 13:21:44 +0200, ofir(dot)manor(at)gmail(dot)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?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Shulgin, Oleksandr 2015-10-26 11:51:01 Re: BUG #13725: Logical Decoding - wrong results with large transactions and unfortunate timing
Previous Message Shulgin, Oleksandr 2015-10-26 11:34:48 Re: BUG #13725: Logical Decoding - wrong results with large transactions and unfortunate timing