"Henryk Szal" <[EMAIL PROTECTED]> writes:
> YES, this feature should affect ALL locks.
> 'Timeout on lock' parameter says to server "I CAN'T WAIT WITH THIS
> TRANSACTION TOO LONG BECAUSE OF (ANY) LOCK",
It still seems to me that what such an application wants is not a lock
timeout at all, but an overall limit on the total elapsed time for the
query. If you can't afford to wait to get a lock, why is it OK to wait
(perhaps much longer) for I/O or computation?
Such a limit would be best handled by sending a query-cancel request
when you run out of patience, it seems to me.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly