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
Subject: Re: How to VACUUM this table? "998994633 estimated total rows"
Date: Mon, 13 Feb 2006 12:35:40 +0000
Message-ID: <f7f6b4c70602130435t16cdaf2eg43c44cda9e9c50e2@mail.gmail.com> (raw)
In-Reply-To: <60ek29e3tw.fsf@dba2.int.libertyrms.com>
References: <43ED56D3.7040404@mediaroot.de>
	<60ek29e3tw.fsf@dba2.int.libertyrms.com>

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.

Best regards,
Guido.


On 2/12/06, Chris Browne <cbbrowne@acm.org> wrote:
>
> an@mediaroot.de (Aldor) writes:
> > I'm just curious about a VACUUM plan of this table:
> >
> > 1st) When to do VAUUM?
> > 2nd) How often to do VACUUM?
> > 3rd) With which postgresql.conf paremeters to set up vacuum?
> > 4th) When to do a VACUUM FULL?
> > 5th) Can autovacuum of 8.1 be used in this case?
> >
> > I'm a little bit afraid about the size of the table, but I think
> > somebody should have a solution...
> >
> > Here is the complete ANALYZE output of the table:
> >
> > INFO:  "tbl1": scanned 300 of 27744713 pages, containing 10802 live rows
> > and 0 dead rows; 300 rows in sample, 998994633 estimated total rows
> >
> > The size of the data is 340 GB, this are 40% of the disk-array.
>
> Vacuuming this table is likely to take a rather long time.  Hours and
> hours; possibly multiple days.
>
> I don't think you'll *ever* want to VACUUM FULL this table; I'm not
> sure you ever want autovacuum to process it either.
>
> I instead think you want to choose a time which seems best to start a
> Very Long Transaction to issue a VACUUM ANALYZE on it.
>
> 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...
>
> I am not sure that's the only opinion you ought to consider on it...
> --
> (reverse (concatenate 'string "moc.enworbbc" "@" "enworbbc"))
> http://cbbrowne.com/info/sap.html
> Why are there interstate highways in Hawaii?
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly
>



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

view thread (5+ messages)  latest in thread

Message-ID: <f7f6b4c70602130435t16cdaf2eg43c44cda9e9c50e2@mail.gmail.com>
Permalink:  ../f7f6b4c70602130435t16cdaf2eg43c44cda9e9c50e2@mail.gmail.com/
Also on:    postgresql.org/message-id/f7f6b4c70602130435t16cdaf2eg43c44cda9e9c50e2@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
  Subject: Re: How to VACUUM this table? "998994633 estimated total rows"
  In-Reply-To: <f7f6b4c70602130435t16cdaf2eg43c44cda9e9c50e2@mail.gmail.com>
  References: <43ED56D3.7040404@mediaroot.de> <60ek29e3tw.fsf@dba2.int.libertyrms.com> <f7f6b4c70602130435t16cdaf2eg43c44cda9e9c50e2@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