Re: lock timeout patch

Поиск
Список
Период
Сортировка
От Robert Treat
Тема Re: lock timeout patch
Дата
Msg-id 1088450694.31168.71.camel@camel
обсуждение исходный текст
Ответ на Re: lock timeout patch  (Satoshi Nagayasu <nagayasus@nttdata.co.jp>)
Ответы Re: lock timeout patch  (Satoshi Nagayasu <nagayasus@nttdata.co.jp>)
Список pgsql-hackers
On Mon, 2004-06-28 at 02:16, Satoshi Nagayasu wrote:
> Tom Lane wrote:
> > I'd accept a mechanism to enforce a timeout at the lock level if you
> > could show me a convincing use-case for lock timeouts instead of
> > statement timeouts, but I don't believe there is one.  I think this
> > proposal is a solution in search of a problem.
> 
> I think statement_timeout and lock_timeout are different.
> 
> If I set statement_timeout to 1000 to detect a lock timeout,
> I can't run a query which takes over 1 sec.
> 
> If a lock wait is occured, I want to detect it immediately,
> but I still want to run a long-running query.
> 

How is your problem not solved by NOWAIT?
http://developer.postgresql.org/docs/postgres/sql-lock.html

Robert Treat
-- 
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Darko Prenosil
Дата:
Сообщение: improper call to spi_printtup ???
Следующее
От: Tom Lane
Дата:
Сообщение: Re: improper call to spi_printtup ???