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 A050BD1CC8D; Wed, 28 Jan 2004 16:33:16 +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 68521-01; Wed, 28 Jan 2004 12:32:45 -0400 (AST)
Received: from ucsns.ucs.co.za (ucs.co.za [196.23.43.2])
	by svr1.postgresql.org (Postfix) with ESMTP
	id 73EFAD1CB50; Wed, 28 Jan 2004 12:32:08 -0400 (AST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by ucsns.ucs.co.za (Postfix) with ESMTP
	id DDBF02C014; Wed, 28 Jan 2004 18:32:04 +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 09501-08; Wed, 28 Jan 2004 18:31:53 +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 455422C187; Wed, 28 Jan 2004 12:11:13 +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 74D75D9E8B; Wed, 28 Jan 2004 12:11:13 +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 4EADF973EC; Wed, 28 Jan 2004 12:11:12 +0200 (SAST)
Date: Wed, 28 Jan 2004 12:11:09 +0200
From: Stef <svb@ucs.co.za>
To: pgsql-performance@postgresql.org
Cc: pgsql-sql@postgresql.org <pgsql-sql@postgresql.org>
Subject: postgres timeout.
Message-Id: <20040128121109.02f554e6.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/')(<lrm)P;
	cAAeen^3Z`d/`t1M`X!B3Mz0L_UUN/n)o%rP)f&Yu}syx]R@;
	&mc=o&]6#=R!4G^lnCE6(%t1w3#VH8; &[NK=XA>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_11_09_+0200_ViNzVdzl_mdLQem4"
X-Virus-Scanned: by amavisd-new at ucs.co.za
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200401/291
X-Sequence-Number: 5465

--Signature=_Wed__28_Jan_2004_12_11_09_+0200_ViNzVdzl_mdLQem4
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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_11_09_+0200_ViNzVdzl_mdLQem4
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iQCVAwUBQBeKwboLc+HYd7LFAQIcMQP+OcTRE3b+Jucn3zg9t9jX33NN0P0dG6sD
62dqfvnNLmQ9Euya0bRENUyv2lHa1SDjfTD9MXmdovBaMI7p/gnEI6OfnUkjSn7v
CwnLKM0xa3nGmmJEzP8/km+pg2527E2N9CiXSt1ClQ396i/FcZDU/74MkG6r577h
ura7i7kthZ0=
=p3Cg
-----END PGP SIGNATURE-----

--Signature=_Wed__28_Jan_2004_12_11_09_+0200_ViNzVdzl_mdLQem4--