From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Christensen <david@endpoint.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16676: SELECT ... FETCH FIRST ROW WITH TIES FOR UPDATE SKIP LOCKED locks rows it doesn't return
Date: Mon, 19 Oct 2020 19:07:10 -0400
Message-ID: <565608.1603148830@sss.pgh.pa.us> (raw)
In-Reply-To: <4143F72C-37BA-43B3-A768-259907CBA985@endpoint.com>
References: <16676-fd62c3c835880da6@postgresql.org>
<4143F72C-37BA-43B3-A768-259907CBA985@endpoint.com>
David Christensen <david@endpoint.com> writes:
> Proposed fix:
> Reorder Limit/LockRows nodes to prevent locking extra tuples in FETCH FIRST WITH TIES
Isn't that going to break more cases than it fixes?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, david@endpoint.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16676: SELECT ... FETCH FIRST ROW WITH TIES FOR UPDATE SKIP LOCKED locks rows it doesn't return
In-Reply-To: <565608.1603148830@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox