X-Original-To: pgsql-sql@postgresql.org
Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id B5C26474E4F
	for <pgsql-sql@postgresql.org>; Fri,  7 Feb 2003 06:39:36 -0500 (EST)
Received: from fzkmail2.fzk.de (fzkmail2.fzk.de [141.52.27.52])
	by postgresql.org (Postfix) with SMTP id 4575F474E44
	for <pgsql-sql@postgresql.org>; Fri,  7 Feb 2003 06:39:24 -0500 (EST)
Received: FROM resy5.fzk.de BY fzkmail2.fzk.de ;
 Fri Feb 07 12:39:05 2003 +0100
Received: œby rodos.fzk.de with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id MAA15612; Fri, 7 Feb 2003 12:39:04 +0100 (MET)
Message-ID: <3E439AD8.7E3C006@rodos.fzk.de>
Date: Fri, 07 Feb 2003 12:39:04 +0100
From: Christoph Haller <ch@rodos.fzk.de>
X-Mailer: Mozilla 4.77 [en] (X11; U; HP-UX B.10.20 9000/780)
X-Accept-Language: en
MIME-Version: 1.0
To: jasiek@klaster.net
Cc: pgsql-sql@postgresql.org
Subject: Re: Lock timeout detection in postgres 7.3.1
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200302/150
X-Sequence-Number: 11548

>
> 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
>
Thanks Tomasz for pointing this out.
STATEMENT_TIMEOUT is exactly what I was looking for.
I should have had a look into the 7.3 Doc on my own.

Regards, Christoph