Re: SELECT FOR UPDATE NOWAIT
От | Paulo Scardine |
---|---|
Тема | Re: SELECT FOR UPDATE NOWAIT |
Дата | |
Msg-id | 014401c3514c$3c915e30$63000a0a@cimed.ind.br обсуждение исходный текст |
Ответ на | Re: SELECT FOR UPDATE NOWAIT (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: SELECT FOR UPDATE NOWAIT
|
Список | pgsql-hackers |
> My guess is that we will implement it was a SET variable so it can > control FOR UPDATE/LOCK/UPDATE/DELETE. > > Added to TODO: > > Add GUC variable to prevent waiting on locks Interesting. I have a lot of potentially dumb questions: - Is this easier to implement as a user variable than in the parser or is some kind of police (SQL compliance, etc.)? - These locks are grant by LockAcquire() or by higher level functions? - Where is the best place to put this? TIA, -- Paulo Scardine --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.490 / Virus Database: 289 - Release Date: 16/6/2003
В списке pgsql-hackers по дате отправления: