X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 3858F474E4F for ; Fri, 7 Feb 2003 05:26:38 -0500 (EST) Received: from serwer.skawsoft.com.pl (serwer.skawsoft.com.pl [213.25.37.66]) by postgresql.org (Postfix) with ESMTP id 75783474E44 for ; Fri, 7 Feb 2003 05:26:37 -0500 (EST) Received: from klaster.net (pe140.krakow.cvx.ppp.tpnet.pl [213.76.40.140]) by serwer.skawsoft.com.pl (Postfix) with ESMTP id 2B4EB2B85D; Fri, 7 Feb 2003 11:19:34 +0100 (CET) Message-ID: <3E438A7D.1020103@klaster.net> Date: Fri, 07 Feb 2003 11:29:17 +0100 From: Tomasz Myrta User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; PL; rv:1.1) Gecko/20020826 X-Accept-Language: pl, en-us, en MIME-Version: 1.0 To: Christoph Haller Cc: pgsql-sql@postgresql.org, shariq77@yahoo.com, lud_nowhere_man@yahoo.com Subject: Re: Lock timeout detection in postgres 7.3.1 References: <3E42512D.D6014A75@rodos.fzk.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/147 X-Sequence-Number: 11545 Christoph Haller wrote: > 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