Re: pg_class.reltuples not reset by VACUUM? - Mailing list pgsql-admin

From Tom Lane
Subject Re: pg_class.reltuples not reset by VACUUM?
Date
Msg-id 19299.1049829035@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_class.reltuples not reset by VACUUM?  (Jeff Boes <jboes@nexcerpt.com>)
Responses Re: pg_class.reltuples not reset by VACUUM?  (Jeff Boes <jboes@nexcerpt.com>)
List pgsql-admin
Jeff Boes <jboes@nexcerpt.com> writes:
> Well, here's the present state of the table, 24 hours later:

> # select count(*) from job_queue;
>  count
> -------
>   2369
> (1 row)

> # vacuum analyze verbose job_queue;

> NOTICE:  --Relation job_queue--
> NOTICE:  Pages 6831: Changed 2, Empty 0; Tup 358441: Vac 0, Keep 356048,
> UnUsed 5.
>     Total CPU 0.00s/0.15u sec elapsed 0.16 sec.

Yup, you definitely have a big problem with dead-but-unreclaimed tuples.
Look for some client that's holding an open transaction for long
periods.

            regards, tom lane


pgsql-admin by date:

Previous
From: Michael Brusser
Date:
Subject: Re: How does PostgreSQL treat null values in unique composite
Next
From: Jeff Boes
Date:
Subject: Re: pg_class.reltuples not reset by VACUUM?