Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified
От | David Christensen |
---|---|
Тема | Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified |
Дата | |
Msg-id | CAOxo6XKFb5P5haRU+rZ1szF0-RDKCQ2kkW3utN1eLaPo3pkHZw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified
|
Список | pgsql-hackers |
On Mon, Aug 30, 2021 at 3:51 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > On 2021-Aug-13, David Christensen wrote: > > > Both bugs #16676[1] and #17141[2] illustrate that the combination of > > SKIP LOCKED and FETCH FIRST WITH TIES break expectations when it comes > > to rows returned to other sessions accessing the same row. Since this > > situation is detectable from the syntax and hard to fix otherwise, > > forbid for now, with the potential to fix in the future. > > I think we should do this, given that it has show potential to bite > people. We should also add a small mentioned to this in the docs, as in > the attached. > > What do others think? The patch I included had a doc mention in roughly the same place (at least the same file), but I'm not tied to the wording I used (and I may have missed more than one spot that might be appropriate). In any case, +1. David
В списке pgsql-hackers по дате отправления: