Re: SKIP LOCKED DATA (work in progress)
От | Thomas Munro |
---|---|
Тема | Re: SKIP LOCKED DATA (work in progress) |
Дата | |
Msg-id | CADLWmXUuy0w+kM8-5sf=oW-ZwEtKK0GTjfGxUWXC_EduOYBwAw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: SKIP LOCKED DATA (work in progress) (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: SKIP LOCKED DATA (work in progress)
Re: SKIP LOCKED DATA (work in progress) |
Список | pgsql-hackers |
On 23 May 2014 21:18, Robert Haas <robertmhaas@gmail.com> wrote: > On Fri, May 23, 2014 at 3:24 PM, Simon Riggs <simon@2ndquadrant.com> wrote: >> PostgreSQL already chose to follow the Oracle syntax when we >> implemented NOWAIT. So my proposal is that we follow the Oracle syntax >> again and use the words SKIP LOCKED. >> >> I don't see any advantage in inventing new syntax that leaves us >> incompatible with Oracle, nor do I see any need to be compatible with >> both Oracle and DB2 since the latter is much less likely to gain us >> anything in practice. > > +1. Hello Please find attached a rebased version of my SKIP LOCKED patch (formerly SKIP LOCKED DATA), updated to support only the Oracle-like syntax. I posted a small test program here: https://github.com/macdice/skip-locked-tests Would anyone who is interested in a SKIP LOCKED feature and attending the CHAR(14)/PGDay UK conference next week be interested in a birds-of-a-feather discussion? Best regards, Thomas Munro
Вложения
В списке pgsql-hackers по дате отправления: