Re: Rows go missing when selecting "for update" after savepoint "play"

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Rows go missing when selecting "for update" after savepoint "play"
Date: 2016-10-06 19:49:03
Message-ID: 20161006194903.GA722217@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)alvh(dot)no-ip(dot)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

In response to

Responses

Browse pgsql-bugs by date

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