Re: Rows go missing when selecting "for update" after savepoint "play"
| От | hubert depesz lubaczewski |
|---|---|
| Тема | Re: Rows go missing when selecting "for update" after savepoint "play" |
| Дата | |
| Msg-id | 20161007121051.doxsi24fyrvyytft@depesz.com обсуждение |
| Ответ на | Re: Rows go missing when selecting "for update" after savepoint "play" (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Список | 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@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. 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
В списке pgsql-bugs по дате отправления: