Re: Rows go missing when selecting "for update" after savepoint "play" - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: Rows go missing when selecting "for update" after savepoint "play"
Date
Msg-id 20161006194903.GA722217@alvherre.pgsql
Whole thread Raw
In response to Re: Rows go missing when selecting "for update" after savepoint "play"  (hubert depesz lubaczewski <depesz@depesz.com>)
Responses Re: Rows go missing when selecting "for update" after savepoint "play"
List pgsql-bugs
hubert depesz lubaczewski wrote:
> On Thu, Oct 06, 2016 at 08:05:33PM +0200, hubert depesz lubaczewski wrote:
> > Used postgresql: 9.5.4 (from pgdg apt archive)
> > system: ubuntu trusty
>
> some more tests showed that the problem is also missing in 9.4 and 9.6,
> so it looks like it was introduced in 9.5, and then fixed in 9.6...

I think this is the bug fixed by this commit

commit f337658850801706334fcfec07928a804fb4e24f
Author:     Alvaro Herrera <alvherre@alvh.no-ip.org>
AuthorDate: Fri Sep 9 15:54:29 2016 -0300
CommitDate: Fri Sep 9 15:54:29 2016 -0300

    Fix locking a tuple updated by an aborted (sub)transaction


So you're now "Waiting for 9.5.5", I'm afraid.

--
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-bugs by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: Rows go missing when selecting "for update" after savepoint "play"
Next
From: 厚积薄发
Date:
Subject: When I set the synchronous_standby_names and synchronous_commit to off, the replication query state also show in sync mode.