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

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: David Christensen <david(dot)christensen(at)crunchydata(dot)com>
Cc: 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-01 21:33:01
Message-ID: 202110012133.rysqravhpzbc@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
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 —
"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)

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Bossart, Nathan 2021-10-01 21:35:52 Re: Enabling deduplication with system catalog indexes
Previous Message Bossart, Nathan 2021-10-01 21:21:04 Re: parallelizing the archiver