[PATCH] Error out if SKIP LOCKED and WITH TIES are both specified - Mailing list pgsql-hackers

From David Christensen
Subject [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified
Date
Msg-id CAOxo6XLPccCKru3xPMaYDpa+AXyPeWFs+SskrrL+HKwDjJnLhg@mail.gmail.com
Whole thread Raw
Responses 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  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List 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

pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Multiple Postgres process are running in background
Next
From: Andrew Dunstan
Date:
Subject: Re: Default to TIMESTAMP WITH TIME ZONE?