From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tomasz Myrta <jasiek@klaster.net>
Cc: Christoph Haller <ch@rodos.fzk.de>
Cc: pgsql-sql@postgresql.org
Cc: shariq77@yahoo.com
Cc: lud_nowhere_man@yahoo.com
Subject: Re: Lock timeout detection in postgres 7.3.1
Date: Tue, 11 Feb 2003 22:00:55 -0500 (EST)
Message-ID: <200302120300.h1C30t224373@candle.pha.pa.us> (raw)
In-Reply-To: <3E438A7D.1020103@klaster.net>
Tomasz Myrta wrote:
> Christoph Haller wrote:
> <cut>
> > Yupp, I agree.
> > But from former DBMS I was dealing with,
> > I know this SET TIMEOUT called feature, which if properly set
> > terminated processes like that hanging on T2.
> > Is there something comparable within Postgres?
>
> PostgreSQL 7.3 Documentation
> 3.4. Run-time Configuration
> STATEMENT_TIMEOUT (integer)
> Aborts any statement that takes over the specified number of milliseconds. A value of zero turns off the timer.
> DEADLOCK_TIMEOUT (integer)
> This is the amount of time, in milliseconds, to wait on a lock before checking to see if there is a deadlock condition
>
>
> In this case I suppose 2 things:
> - table has a lot of records and you should just wait to finish operation.
> - another query locked the table and it is realy a deadlock
One of the uses of STATEMENT_TIMEOUT is to allow a LOCK or query to fail
if it doesn't complete in a short time. We don't have a special timer
to say if we are waiting on a lock for a specified time --- just a
query-level timer.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: pgman@candle.pha.pa.us, jasiek@klaster.net, ch@rodos.fzk.de, shariq77@yahoo.com, lud_nowhere_man@yahoo.com
Subject: Re: Lock timeout detection in postgres 7.3.1
In-Reply-To: <200302120300.h1C30t224373@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox