Quick Links

Re: can we add SKIP LOCKED to UPDATE?

From:	Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:	德哥 <digoal(at)126(dot)com>
Cc:	"pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject:	Re: can we add SKIP LOCKED to UPDATE?
Date:	2015-11-09 17:06:12
Message-ID:	27324.1447088772@sss.pgh.pa.us
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

=?GBK?B?tcK45w==?= <digoal(at)126(dot)com> writes:
> PostgreSQL 9.5 added skip locked to select for update to improve concurrency performance, but why not add it to update sql?

Seems like you'd have unpredictable results from the update then.

regards, tom lane

In response to

can we add SKIP LOCKED to UPDATE? at 2015-11-09 05:00:30 from 德哥

Responses

Re: can we add SKIP LOCKED to UPDATE? at 2015-11-09 17:25:47 from Simon Riggs
Re: can we add SKIP LOCKED to UPDATE? at 2015-11-09 17:38:45 from Jeff Janes

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Pavel Stehule	2015-11-09 17:18:18	Re: proposal: multiple psql option -c
Previous Message	Torsten Zuehlsdorff	2015-11-09 17:00:33	Re: Extracting fields from 'infinity'::TIMESTAMP[TZ]