Re: [Postgresql 8.2.3] autovacuum starting up even after disabling ?

From: Dushyanth <dushyanth(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: [Postgresql 8.2.3] autovacuum starting up even after disabling ?
Date: 2008-07-08 08:30:26
Message-ID: loom.20080708T081617-194@post.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

Tom Lane <tgl <at> sss.pgh.pa.us> writes:
> Dushyanth <dushyanth <at> gmail.com> writes:
> >> Tom Lane <tgl <at> sss.pgh.pa.us> writes:
> >> Then the only other possibility is that autovacuum is being launched to
> >> prevent XID wraparound. Are there any tables in that database with
> >> particularly old relfrozenxid?
>
> > Below are the unique age(relfrozenxid) values that i see from the above query
>
> > 140835139
> > 150945753
> > 185741480
>
> Hmph. Does pg_database.datfrozenxid agree with that?

Yes.

/usr/local/postgres/current/bin/psql -t -U postgres -d template1 -c"SELECT
datname, age(datfrozenxid) FROM pg_database;"
postgres | 169111100
db1 | 169288969
db2 | 192179807
template1 | 153877757
template0 | 195372755

autovacuum seems to run on db1 and db2. Iam attempting to get the table details
as Alvaro requested

On a side note, i see connections in '<IDLE> in transaction' state. Can this
cause such behaviour ?

TIA
Dushyanth

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Simon Riggs 2008-07-08 08:36:12 Re: please explain vacuum with WAL
Previous Message Dmitry Melekhov 2008-07-08 08:09:06 please explain vacuum with WAL