Skip site navigation (1) Skip section navigation (2)

Re: vacuumdb hanging database cluster

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: vacuumdb hanging database cluster
Date: 2004-07-27 01:00:26
Message-ID: 15438.1090890026@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Steve Crawford <scrawford(at)pinpointresearch(dot)com> writes:
>>> I tracked down the process that was "idle in transaction" and it
>>> was a pg_dump process running on another machine.
>> 
>> What was it waiting on?

> Beats the heck out of me. We periodically dump some selected small 
> tables via a script using:
> pg_dump -i -h $dbhost -U $dbuser -t $dumptable > dumpfile

> It's very vanilla and generally works fine but sometimes (perhaps 1 
> per 1000+ runs) ends up idle in transaction. I'm going to take a much 
> closer look at pg_locks next time it happens.

If it is "idle in transaction" and not "<something> waiting" then it is
not blocked waiting for someone's lock, so pg_locks is unlikely to yield
the answer.  I think it's got to be something funny on the pg_dump side.
Or maybe a communications problem?

			regards, tom lane

In response to

pgsql-general by date

Next:From: Tom LaneDate: 2004-07-27 01:09:12
Subject: Re: estimating table size
Previous:From: Ian BarwickDate: 2004-07-26 22:39:06
Subject: Re: estimating table size

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group