Re: How to VACUUM this table? "998994633 estimated total rows"

So this presents the fact that pg_stattuple should prevent and guess [taking
a sample?] that a table needs an urgent lookup instead of ending the scan
and presenting real numbers?

g.-

On 2/13/06, Chris Browne <cbbrowne(at)acm(dot)org> wrote:
>
> gbarosio(at)gmail(dot)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 you shall 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.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>

--
/"\ ASCII Ribbon Campaign .
\ / - NO HTML/RTF in e-mail .
X - NO Word docs in e-mail .
/ \ -----------------------------------------------------------------