| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Oskari Saarenmaa <os(at)aiven(dot)io>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Tripp <peter(at)chartio(dot)com>, Virendra Negi <virendra(at)idyllic-software(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14150: Attempted to delete invisible tuple |
| Date: | 2016-08-18 20:57:42 |
| Message-ID: | CAM3SWZTo9RajJ_kFpBSW71Uy06npkfuXrJoXqwassYhgbqfu=g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Aug 18, 2016 at 1:43 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> You could possibly try to force a single ordering by inserting a sleep
>> into some step of the test --- we have some other isolation tests that
>> do it that way. But it's hard to predict how much sleep is enough.
>
> I don't think it's applicable here - s2/3 are woken up by the same lock
> release. The order in which the OS lets them run primarily determines
> the result visibility. A sleep wouldn't hide the difference in output
> order afaics. I guess we could hide the combined steps (insert & sleep)
> in a function, but ...
There is an argument to be made for fixing isolationtester to
accommodate this kind of thing.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-08-18 21:09:27 | Re: BUG #14150: Attempted to delete invisible tuple |
| Previous Message | Andres Freund | 2016-08-18 20:43:42 | Re: BUG #14150: Attempted to delete invisible tuple |