From: Tomasz Myrta <jasiek@klaster.net>
To: 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: Fri, 07 Feb 2003 11:29:17 +0100
Message-ID: <3E438A7D.1020103@klaster.net> (raw)
References: <3E42512D.D6014A75@rodos.fzk.de>
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
Regards,
Tomasz Myrta
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: 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: <3E438A7D.1020103@klaster.net>
* 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