X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 1B5999DCBC6 for ; Mon, 13 Feb 2006 16:45:07 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 09879-06 for ; Mon, 13 Feb 2006 16:45:04 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.193]) by postgresql.org (Postfix) with ESMTP id 436409DC881 for ; Mon, 13 Feb 2006 16:44:59 -0400 (AST) Received: by uproxy.gmail.com with SMTP id u40so711268ugc for ; Mon, 13 Feb 2006 12:45:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=hbcc2VUiLC22wMKc6Z9Nf0hcUwJ70Vw9+D0qkqWVScfPtKM59ti1XzldWI+fbfx/2FBjCeAVDV5Xoaq37IbUTzw8ns0pFSUQ8ON141x6/jR8CrW+zVn89MiKAD0+946mBVewD13lhC7FJyHY5IC8t5rCXX3jy1OtwF8i1P4Hzok= Received: by 10.67.30.9 with SMTP id h9mr1378937ugj; Mon, 13 Feb 2006 12:45:00 -0800 (PST) Received: by 10.66.224.9 with HTTP; Mon, 13 Feb 2006 12:45:00 -0800 (PST) Message-ID: Date: Mon, 13 Feb 2006 20:45:00 +0000 From: Guido Barosio To: Chris Browne Subject: Re: How to VACUUM this table? "998994633 estimated total rows" Cc: pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org In-Reply-To: <60k6bzcnje.fsf@dba2.int.libertyrms.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_25452_32362148.1139863500209" References: <43ED56D3.7040404@mediaroot.de> <60ek29e3tw.fsf@dba2.int.libertyrms.com> <60k6bzcnje.fsf@dba2.int.libertyrms.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.361 required=5 tests=[AWL=0.360, HTML_MESSAGE=0.001] X-Spam-Score: 0.361 X-Spam-Level: X-Archive-Number: 200602/168 X-Sequence-Number: 20589 ------=_Part_25452_32362148.1139863500209 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline So this presents the fact that pg_stattuple should prevent and guess [takin= g 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 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 dea= d > 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=3D"cbbrowne" and tld=3D"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 . / \ ----------------------------------------------------------------- ------=_Part_25452_32362148.1139863500209 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline So this presents the fact that pg_stattuple should prevent and guess [takin= g a sample?]  that a table needs an urgent lookup instead of ending th= e 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 dea= d 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 so= ftware, 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 al= l 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=3D"cbbr= owne" and tld=3D" cbbrowne.com" in name ^ "@&qu= ot; ^ tld;;
http://cbbrown= e.com/info/lsf.html
Philosophy is a game with objectives and no rule= s.
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 .
/ \ -----------------------------------------------------------= ------ ------=_Part_25452_32362148.1139863500209--