Re: SELECT FOR UPDATE NOWAIT
| От | Tom Lane |
|---|---|
| Тема | Re: SELECT FOR UPDATE NOWAIT |
| Дата | |
| Msg-id | 15579.1058987198@sss.pgh.pa.us обсуждение |
| Ответ на | Re: SELECT FOR UPDATE NOWAIT ("Paulo Scardine" <paulos@cimed.ind.br>) |
| Ответы |
Re: SELECT FOR UPDATE NOWAIT
|
| Список | 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 по дате отправления: