HI,
My case is concurrency update one row(for exp 1000 client update the same row
at the same time), and target is prevent waiting for waiters(quick return to
client).
use advisory lock is a method, for quick return. but not good , must use
function(to reduce consume between client-db network).
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
