X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 0281CD1CA54; Wed, 28 Jan 2004 16:59:54 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 80955-05; Wed, 28 Jan 2004 12:59:23 -0400 (AST) Received: from ucsns.ucs.co.za (ucs.co.za [196.23.43.2]) by svr1.postgresql.org (Postfix) with ESMTP id 0E487D1CADF; Wed, 28 Jan 2004 12:59:22 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by ucsns.ucs.co.za (Postfix) with ESMTP id 0CF0F2BFCF; Wed, 28 Jan 2004 18:59:20 +0200 (SAST) Received: from ucsns.ucs.co.za ([127.0.0.1]) by localhost (ucsns.ucs.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10598-03; Wed, 28 Jan 2004 18:59:08 +0200 (SAST) Received: from ucspost.ucs.co.za (mailgw1.ucs.co.za [196.23.43.253]) by ucsns.ucs.co.za (Postfix) with ESMTP id D79F92C2D8; Wed, 28 Jan 2004 12:47:26 +0200 (SAST) Received: from jhb.ucs.co.za (jhb.ucs.co.za [172.31.1.3]) by ucspost.ucs.co.za (Postfix) with ESMTP id DDC5FD9EA9; Wed, 28 Jan 2004 12:47:26 +0200 (SAST) Received: from svb.ucs.co.za (svb.ucs.co.za [172.31.1.148]) by jhb.ucs.co.za (Postfix) with SMTP id 1C3F7973EC; Wed, 28 Jan 2004 12:47:26 +0200 (SAST) Date: Wed, 28 Jan 2004 12:47:22 +0200 From: Stef To: pg-perform Cc: pgsql-sql@postgresql.org Subject: Re: postgres timeout. [SOLVED] Message-Id: <20040128124722.78fe5dc0.svb@ucs.co.za> In-Reply-To: <20040128121217.2e4aceef.svb@ucs.co.za> References: <20040128121109.02f554e6.svb@ucs.co.za> <20040128121217.2e4aceef.svb@ucs.co.za> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) User-Agent: sillypheed-claws (anti-aliased) X-Face: GFoC95e6r)_TTG>n~=uFLojP=O~4W@Ms]>:.DMm/')(z3\Mwj^XP@? Q:3";lD.OM1"^mDu}2NJ@US:)dO:U*iY5EM50&Tx. X-Operating-System: sid X-X-X: _-^-_ Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Wed__28_Jan_2004_12_47_22_+0200_ob+DRIW2rsuQYY+H" X-Virus-Scanned: by amavisd-new at ucs.co.za X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/293 X-Sequence-Number: 5467 --Signature=_Wed__28_Jan_2004_12_47_22_+0200_ob+DRIW2rsuQYY+H Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Hi all, It seems I always find a solution just after panicking a little bit. Anyway, I found that statement_timeout solved my problem. When I tested it earlier, I actually made an error, and skipped it as a possible solution. Cheers Stef Stef mentioned : => Forgot to mention that I use postgres 7.3.4 => => Stef mentioned : => => Hi all , => => => => I'm trying to find out if there is a specific setting => => to make transactions time out faster in a scenario => => where there's an update on a table in a transaction => => block, and another update process tries to update => => the same column. => => => => It looks like the second process will wait until you => => end the transaction block in the first transaction. => => => => I've looked at the deadlock timeout parameter and => => other parameters, but I don't think I found what => => I'm looking for. => => => => I basically need to be able to let the second process => => exit with an error after waiting 5 - 10 seconds. => => => => Please can someone help? => => => => Kind Regards => => Stefan => => => --Signature=_Wed__28_Jan_2004_12_47_22_+0200_ob+DRIW2rsuQYY+H Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQCVAwUBQBeTProLc+HYd7LFAQKu6wP/Y1mwesFbpeVYk/cEIS7qsbxPwcabByfQ c4Lkitlp7zs2pdMtlwCl9PAMX+t09q0bdffon7SAo14taIKFvvcLMkrobls4TMEZ k0fmV7qChlv3oLens71QezQDphnvdOYMCyX1cNLwFNJBNte8EfxzbJNPrwgBuepB dixrYGexRe4= =d4H3 -----END PGP SIGNATURE----- --Signature=_Wed__28_Jan_2004_12_47_22_+0200_ob+DRIW2rsuQYY+H--