Re: Idle in transaction ???? - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: Idle in transaction ????
Date
Msg-id 20011116014521.D3148@svana.org
Whole thread Raw
In response to Idle in transaction ????  ("Steve Brett" <steve.brett@e-mis.com>)
List pgsql-general
On Wed, Nov 14, 2001 at 03:21:36PM -0000, Steve Brett wrote:
> we've just started using zeos postgresql db components in delphi and i've
> noticed that vacuum is hanging in postgres.
>
> if i do ps auxf i get the following
>
> postgres   332  0.0  0.5 13832 1344 ?        S    14:24   0:00
> /usr/local/pgsql/bin/./postmaster -i -o -F -B 1024 -N 128
> postgres   722  0.0  1.3 14704 3496 ?        S    14:55   0:00  \_ postgres:
> postgres ohm 10.139.13.112 idle in transact
> postgres   752  0.1  1.8 14580 4740 ?        S    15:04   0:01  \_ postgres:
> iain ohm 10.139.13.187 idle
> postgres  1086  0.5  1.3 14620 3360 ?        S    15:23   0:00  \_ postgres:
> postgres ohm [local] VACUUM waiting
>
> it's the 'idle in transact' that i'm puzzled about and i'm assuming it's
> idel within a transaction block ...

You've got something with an active transaction somewhere and VACUUM is
waiting for it to finish. Find whichever process is guilty and fix it to
commit the transaction.

I think the new vacuum in 7.2 is less picky about locks and will simply skip
tables it can't get a lock on.
--
Martijn van Oosterhout <kleptog@svana.org>
http://svana.org/kleptog/
> Magnetism, electricity and motion are like a three-for-two special offer:
> if you have two of them, the third one comes free.

pgsql-general by date:

Previous
From: tony
Date:
Subject: Re: Ultradev and PostgreSQL on SuSE
Next
From: Martijn van Oosterhout
Date:
Subject: Re: UPDATE w/ subselect doing locking