Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: David Christensen <david(dot)christensen(at)crunchydata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified
Date: 2021-10-02 17:24:18
Message-ID: 20211002172418.GA9891@ahch-to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-10-02 17:32:57 Re: BUG #17212: pg_amcheck fails on checking temporary relations
Previous Message Justin Pryzby 2021-10-02 15:41:54 Re: should frontend tools use syncfs() ?