From: Christoph Haller <ch@rodos.fzk.de>
To: pgsql-sql@postgresql.org
Cc: hhiturre@yahoo.com.ar
Subject: Re: Problems with Transactions
Date: Wed, 12 Feb 2003 15:18:38 +0100
Message-ID: <3E4A57BE.B3A1CC87@rodos.fzk.de> (raw)
>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ch@rodos.fzk.de, hhiturre@yahoo.com.ar
Subject: Re: Problems with Transactions
In-Reply-To: <3E4A57BE.B3A1CC87@rodos.fzk.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox