Re: SKIP LOCKED DATA (work in progress)
| От | Thomas Munro |
|---|---|
| Тема | Re: SKIP LOCKED DATA (work in progress) |
| Дата | |
| Msg-id | CADLWmXXJtq1OsxmrfdNHA9hTLRP+v5mpq5QjxSXF+BeXX+hOow@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: SKIP LOCKED DATA (work in progress) (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Ответы |
Re: SKIP LOCKED DATA (work in progress)
|
| Список | pgsql-hackers |
On 25 August 2014 02:57, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > Thomas Munro wrote: >> The difficulty of course will be testing all these racy cases reproducibly... > > Does this help? > http://www.postgresql.org/message-id/51FB4305.3070600@2ndquadrant.com > The useful trick there is forcing a query to get its snapshot and then > go to sleep before actually doing anything, by way of an advisory lock. Yes it does, thanks Alvaro and Craig. I think the attached spec reproduces the problem using that trick, ie shows NOWAIT blocking, presumably in EvalPlanQualFetch (though I haven't stepped through it with a debugger yet). I'm afraid I'm out of Postgres hacking cycles for a few days, but next weekend I should have a new patch that fixes this by teaching EvalPlanQualFetch about wait policies, with isolation tests for NOWAIT and SKIP LOCKED. Best regards, Thomas Munro
Вложения
В списке pgsql-hackers по дате отправления: