Re: lock timeout patch - Mailing list pgsql-hackers

From Satoshi Nagayasu
Subject Re: lock timeout patch
Date
Msg-id 40E0AAF6.6020106@noanet06.noanet.nttdata.co.jp
Whole thread Raw
In response to Re: lock timeout patch  (Robert Treat <xzilla@users.sourceforge.net>)
List pgsql-hackers
Robert Treat wrote:
>>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

I agree that it's one of the solutions when we use LOCK explicitly.
But LOCK does only lock a whole table, doesn't it?

-- 
NAGAYASU Satoshi <nagayasus@nttdata.co.jp>


pgsql-hackers by date:

Previous
From: "Darko Prenosil"
Date:
Subject: Re: improper call to spi_printtup ???
Next
From: Satoshi Nagayasu
Date:
Subject: Re: lock timeout patch