pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Guido Barosio <gbarosio@gmail.com>
To: Chris Browne <cbbrowne@acm.org>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: How to VACUUM this table? "998994633 estimated total rows"
Date: Mon, 13 Feb 2006 20:45:00 +0000
Message-ID: <f7f6b4c70602131245u3503223ft382e860420a410bc@mail.gmail.com> (raw)
In-Reply-To: <60k6bzcnje.fsf@dba2.int.libertyrms.com>
References: <43ED56D3.7040404@mediaroot.de>
	<60ek29e3tw.fsf@dba2.int.libertyrms.com>
	<f7f6b4c70602130435t16cdaf2eg43c44cda9e9c50e2@mail.gmail.com>
	<60k6bzcnje.fsf@dba2.int.libertyrms.com>

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@acm.org> wrote:
>
> 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 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 .
/ \ -----------------------------------------------------------------

view thread (5+ messages)

Message-ID: <f7f6b4c70602131245u3503223ft382e860420a410bc@mail.gmail.com>
Permalink:  ../f7f6b4c70602131245u3503223ft382e860420a410bc@mail.gmail.com/
Also on:    postgresql.org/message-id/f7f6b4c70602131245u3503223ft382e860420a410bc@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: gbarosio@gmail.com, cbbrowne@acm.org, pgsql-hackers@postgresql.org
  Subject: Re: How to VACUUM this table? "998994633 estimated total rows"
  In-Reply-To: <f7f6b4c70602131245u3503223ft382e860420a410bc@mail.gmail.com>
  References: <43ED56D3.7040404@mediaroot.de> <60ek29e3tw.fsf@dba2.int.libertyrms.com> <f7f6b4c70602130435t16cdaf2eg43c44cda9e9c50e2@mail.gmail.com> <60k6bzcnje.fsf@dba2.int.libertyrms.com> <f7f6b4c70602131245u3503223ft382e860420a410bc@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox