Re: LOCK for non-tables
От | Tom Lane |
---|---|
Тема | Re: LOCK for non-tables |
Дата | |
Msg-id | 10278.1295035552@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: LOCK for non-tables (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: LOCK for non-tables
|
Список | pgsql-hackers |
Simon Riggs <simon@2ndQuadrant.com> writes: > On Fri, 2011-01-14 at 14:48 -0500, Tom Lane wrote: >> In any case I'd rather break apps using "LOCK foo NOWAIT" than break >> every application using any form of LOCK at all, which is what I think >> your proposal will amount to in practice. > Can I suggest that we don't break anything at all? > pg_lock_object(objectname, objecttype, mode); > or > pg_lock_sequence(name, mode); > is all we need... No, that will not work at all. LOCK has to be a utility command. A function called by SELECT isn't a substitute, because SELECT will acquire a transaction snapshot before executing the function, and that breaks many use cases for locks. regards, tom lane
В списке pgsql-hackers по дате отправления: