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






-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Reply via email to