| From: | David Christensen <david(dot)christensen(at)crunchydata(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified |
| Date: | 2021-08-13 16:16:18 |
| Message-ID: | CAOxo6XLPccCKru3xPMaYDpa+AXyPeWFs+SskrrL+HKwDjJnLhg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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://www.postgresql.org/message-id/16676-fd62c3c835880da6%40postgresql.org
[2]
https://www.postgresql.org/message-id/17141-913d78b9675aac8e%40postgresql.org
Proposed backpatch to 13.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Error-out-if-SKIP-LOCKED-and-WITH-TIES-are-both-spec.patch | application/octet-stream | 3.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-08-13 16:23:19 | Re: Default to TIMESTAMP WITH TIME ZONE? |
| Previous Message | Ranier Vilela | 2021-08-13 16:16:07 | Re: Multiple Postgres process are running in background |