can we add SKIP LOCKED to UPDATE?

From: 德哥 <digoal(at)126(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: can we add SKIP LOCKED to UPDATE?
Date: 2015-11-09 05:00:30
Message-ID: 68135042.7944.150ea9df17e.Coremail.digoal@126.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

HI,
PostgreSQL 9.5 added skip locked to select for update to improve concurrency performance, but why not add it to update sql?
this is an application case, some body will update a tuple at the same time, so the RT for waiter is big, I use function and select for update nowait or advisory lock , can improve concurrency , but it's not very pure for developer.
http://blog.163.com/digoal(at)126/blog/static/16387704020158149538415/

--
公益是一辈子的事,I'm Digoal,Just Do It.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vitaly Burovoy 2015-11-09 05:15:16 Returning 'Infinity'::TIMESTAMPTZ from "to_timestamp" function
Previous Message Amit Kapila 2015-11-09 04:46:51 Re: eXtensible Transaction Manager API