The following bug has been logged online:

Bug reference: 1390
Logged by: Tristen Ennemuist
Email address: tristen (AT) mangolist (DOT) com
PostgreSQL version: 7.4
Operating system: linux
Description: Lock Timeout
Details:

This is more of an enhancement request, not a bug.

It would be nice if a lock timeout was implemented.

Currently postgresql causes a process to wait indefinitely until the record
becomes available.

I suppose there are many arguments for and against lock timeouts - but if it
were configurable, then developers could have the luxury of choice.

It would therefore be ideal if a LOCK_TIMEOUT (or similar) parameter (in
milliseconds) could be added to the conf file. A default zero value could
indicate the current indefinite behaviour.

Great product, keep up the good work. I'm currently migrating from MySQL and
this is the one and only explicit functionality compromise I've had to
make.

Can't wait for version 8!

Best regards
Tristen

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

On Wed, Jan 12, 2005 at 01:23:59PM +0000, Tristen Ennemuist wrote:
You might be able to use statement_timeout, although it doesn't
distinguish between waiting for a lock and a query that simply
takes a long time to run.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org)