X-Original-To: pgsql-sql@postgresql.org
Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 0F81B474E5C
	for <pgsql-sql@postgresql.org>; Wed, 12 Feb 2003 09:18:38 -0500 (EST)
Received: from fzkmail2.fzk.de (fzkmail2.fzk.de [141.52.27.52])
	by postgresql.org (Postfix) with SMTP id CB516474E44
	for <pgsql-sql@postgresql.org>; Wed, 12 Feb 2003 09:18:36 -0500 (EST)
Received: FROM resy5.fzk.de BY fzkmail2.fzk.de ;
 Wed Feb 12 15:18:39 2003 +0100
Received: œby rodos.fzk.de with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id PAA21311; Wed, 12 Feb 2003 15:18:38 +0100 (MET)
Message-ID: <3E4A57BE.B3A1CC87@rodos.fzk.de>
Date: Wed, 12 Feb 2003 15:18:38 +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: pgsql-sql@postgresql.org
Cc: hhiturre@yahoo.com.ar
Subject: Re: Problems with Transactions
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200302/239
X-Sequence-Number: 11637

>
> I'm using Postgres 7.2 and i'm having problems with
> transactions. Is there a function or table that
> informs which user is blocking a row?
>
AFAIK, there is no such information available.
Are your problems with transactions coming from
blocked rows?

Maybe this 7.3 feature can help you

>
> 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
>
Regards, Christoph