Re: How to VACUUM this table? "998994633 estimated total rows" - Mailing list pgsql-admin

From Chris Browne
Subject Re: How to VACUUM this table? "998994633 estimated total rows"
Date
Msg-id 60k6bzcnje.fsf@dba2.int.libertyrms.com
Whole thread Raw
In response to How to VACUUM this table? "998994633 estimated total rows"  (Aldor <an@mediaroot.de>)
Responses Re: How to VACUUM this table? "998994633 estimated total rows"  (Guido Barosio <gbarosio@gmail.com>)
List pgsql-admin
gbarosio@gmail.com (Guido Barosio) writes:
> quote: " If you are quite sure it has few if any dead tuples, it might be
> something to try to avoid VACUUMing except as needed to evade the 2^31
> transaction limit..."
> You may use the pg_stattuple software, included in the /contrib . This will show you the current scenery, and whether
youshall clean or not dead tuples. 

The trouble with pg_stattuple() is that running it is virtually as
expensive as running the vacuum.  For a bit table, you pay all the I/O
cost, and any costs of the super-long-running-transaction and don't
even get any cleanup for that cost.
--
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://cbbrowne.com/info/lsf.html
Philosophy is a game with objectives and no rules.
Mathematics is a game with rules and no objectives.

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: constraint_exclusion on OLTP tables
Next
From: Steve Burrows
Date:
Subject: Lost tables in Postgres 7.1