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

From Jaime Casanova
Subject Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified
Date
Msg-id 20211002172418.GA9891@ahch-to
Whole thread Raw
In response to Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Fri, Oct 01, 2021 at 06:33:01PM -0300, Alvaro Herrera wrote:
> 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.
> 

BTW, I just marked this one as committed in CF app

-- 
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: should frontend tools use syncfs() ?
Next
From: Daniel Gustafsson
Date:
Subject: Re: Better context for "TAP tests not enabled" error message