Re: pg_class.reltuples not reset by VACUUM?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Boes <jboes(at)nexcerpt(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_class.reltuples not reset by VACUUM?
Date: 2003-04-08 19:10:35
Message-ID: 19299.1049829035@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Jeff Boes <jboes(at)nexcerpt(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Josh Berkus 2003-04-08 19:15:47 Re: Triggers
Previous Message Michael Brusser 2003-04-08 18:23:35 Re: How does PostgreSQL treat null values in unique composite