Re: case for lock_timeout - Mailing list pgsql-general

From Tom Lane
Subject Re: case for lock_timeout
Date
Msg-id 22337.1088658029@sss.pgh.pa.us
Whole thread Raw
In response to Re: case for lock_timeout  (Rajesh Kumar Mallah <mallah@trade-india.com>)
List pgsql-general
Rajesh Kumar Mallah <mallah@trade-india.com> writes:
> ok, you mean we should put statement timeout with statements
> that potentially lock table exclusively. eg

Actually I think it'd work better to put NOLOCK on the read-only
operations.  Those guys should never fail to get the lock they need
under ordinary circumstances.  If you happen to be running some kind
of schema-altering process in parallel, then the read-only guys will
fail immediately instead of waiting, but AFAICT that's what you wanted.

            regards, tom lane

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: Problems restarting after database crashed (signal
Next
From: "Najib Abi Fadel"
Date:
Subject: Bug in function to_char() !!