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

From Alvaro Herrera
Subject Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified
Date
Msg-id 202110012133.rysqravhpzbc@alvherre.pgsql
Whole thread Raw
In response to [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified  (David Christensen <david.christensen@crunchydata.com>)
Responses Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified  (Jaime Casanova <jcasanov@systemguards.com.ec>)
List 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)



pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: parallelizing the archiver
Next
From: "Bossart, Nathan"
Date:
Subject: Re: Enabling deduplication with system catalog indexes