Error out if SKIP LOCKED and WITH TIES are both specified
Alvaro Herrera <alvherre@alvh.no-ip.org>
Error out if SKIP LOCKED and WITH TIES are both specified 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. [1] https://postgr.es/m/16676-fd62c3c835880da6@postgresql.org [2] https://postgr.es/m/17141-913d78b9675aac8e@postgresql.org Backpatch-through: 13, where WITH TIES was introduced Author: David Christensen <david.christensen@crunchydata.com> Discussion: https://postgr.es/m/CAOxo6XLPccCKru3xPMaYDpa+AXyPeWFs+SskrrL+HKwDjJnLhg@mail.gmail.com
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/ref/select.sgml | modified | +2 −1 |
| src/backend/commands/matview.c | modified | +2 −1 |
| src/backend/parser/gram.y | modified | +15 −0 |
| src/test/regress/expected/limit.out | modified | +5 −0 |
| src/test/regress/sql/limit.sql | modified | +5 −0 |
Documentation touched
Discussion
- [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified 7 messages · 2021-08-13 → 2021-10-02