Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: David Christensen <david.christensen@crunchydata.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-10-01T21:33:01Z
Lists: pgsql-hackers
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. Thank you, pushed with minimal adjustment. -- Álvaro Herrera 39°49'30"S 73°17'W — https://www.EnterpriseDB.com/ "Digital and video cameras have this adjustment and film cameras don't for the same reason dogs and cats lick themselves: because they can." (Ken Rockwell)
Commits
-
Error out if SKIP LOCKED and WITH TIES are both specified
- c6bc655ee2ef 15.0 landed
- 20047609d39c 14.1 landed
- 170206e458bc 13.5 landed