From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(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-07 12:10:51 |
Message-ID: | 20161007121051.doxsi24fyrvyytft@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Oct 06, 2016 at 04:49:03PM -0300, Alvaro Herrera wrote:
> 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.
Thanks a lot. Checked, and it looks that 9.5 HEAD is free of the bug, so
I'll just wait. It's ok.
Best regards,
depesz
From | Date | Subject | |
---|---|---|---|
Next Message | digoal | 2016-10-07 14:54:13 | BUG #14360: snapshot too old bug? cann't reclaim dead tuple after has only xmin's transaction. |
Previous Message | hubert depesz lubaczewski | 2016-10-07 12:09:53 | Re: BUG #14359: serial datatype issue |