Re: lock timeout patch - Mailing list pgsql-hackers

From Dennis Bjorklund
Subject Re: lock timeout patch
Date
Msg-id Pine.LNX.4.44.0406281319470.21809-100000@zigo.dhs.org
Whole thread Raw
In response to Re: lock timeout patch  (Satoshi Nagayasu <nagayasus@nttdata.co.jp>)
Responses Re: lock timeout patch  (Satoshi Nagayasu <nagayasus@nttdata.co.jp>)
List pgsql-hackers
On Mon, 28 Jun 2004, Satoshi Nagayasu wrote:

> 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.

Why is it important what it is that makes your query not return as fast as
you expect? Maybe it's locking, maybe the computer is swapping, maybe it's
just lack of IO to that disk that holds the table, maybe it does a big
sort and have too little sort_mem to do it fast, ...

What makes locking special?

-- 
/Dennis Björklund



pgsql-hackers by date:

Previous
From: Gaetano Mendola
Date:
Subject: Re: warning missing
Next
From: Tom Lane
Date:
Subject: Re: Tablespace permissions issue