Re: SELECT FOR UPDATE NOWAIT - Mailing list pgsql-hackers

From Tom Lane
Subject Re: SELECT FOR UPDATE NOWAIT
Date
Msg-id 15579.1058987198@sss.pgh.pa.us
Whole thread Raw
In response to Re: SELECT FOR UPDATE NOWAIT  ("Paulo Scardine" <paulos@cimed.ind.br>)
Responses Re: SELECT FOR UPDATE NOWAIT  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
"Paulo Scardine" <paulos@cimed.ind.br> writes:
> - Where is the best place to put this?

I think it would be a really *bad* idea to put it in LockAcquire; that
risks breaking things that you don't want broken.

Whether it's special syntax or a GUC variable, the restriction should
only apply to SELECT FOR UPDATE row locks, perhaps user-commanded LOCK
TABLE operations, and maybe one or two other places that are known to
be used only for user-written operations and not for system-initiated
ones.  Those places would need to check whether to do a conditional
or unconditional lock.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Jenny -"
Date:
Subject: ...
Next
From: "Jenny -"
Date:
Subject: how do i turn off the html tags??