Re: [PATCH] Error out if SKIP LOCKED and WITH TIES are both specified
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Michael Paquier <michael@paquier.xyz>
Cc: David Christensen <david.christensen@crunchydata.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-10-01T12:55:02Z
Lists: pgsql-hackers
On 2021-Oct-01, Michael Paquier wrote: > On Mon, Aug 30, 2021 at 03:55:10PM -0500, David Christensen wrote: > > On Mon, Aug 30, 2021 at 3:51 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > >> I think we should do this, given that it has show potential to bite > >> people. We should also add a small mentioned to this in the docs, as in > >> the attached. > >> > >> What do others think? > > There is a CF entry for this patch: > https://commitfest.postgresql.org/34/3286/ > > Alvaro, are you planning to wrap that? I've had mixed feelings about this whole idea, but I think it's the right thing to do. I'll try to get it pushed today. -- Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/ "I can't go to a restaurant and order food because I keep looking at the fonts on the menu. Five minutes later I realize that it's also talking about food" (Donald Knuth)
Commits
-
Error out if SKIP LOCKED and WITH TIES are both specified
- c6bc655ee2ef 15.0 landed
- 20047609d39c 14.1 landed
- 170206e458bc 13.5 landed