From: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alexander Schöcke <asc(at)turtle-entertainment(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Bloated Table |
Date: | 2009-05-27 16:38:04 |
Message-ID: | 1243442284.20786.15.camel@bnicholson-desktop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2009-05-27 at 11:15 -0400, Tom Lane wrote:
> =?iso-8859-1?Q?Alexander_Sch=F6cke?= <asc(at)turtle-entertainment(dot)de> writes:
> > I'm using a view
> > (http://pgsql.tapoueh.org/site/html/news/20080131.bloat.html) to
> > display the bloat (unused disk space) of the tables in a PostgreSQL
> > database.
>
> I wouldn't trust the calculations that view does in the least.
> You might look at contrib/pgstattuple if you want numbers that
> have some relationship to reality (and are correspondingly more
> expensive to get :-()
>
> regards, tom lane
Is the referenced query reliable for even estimating, or is it flat our
wrong?
Co-workers that were PGCon are saying that this is becoming a
popular/accepted way to check for bloated tables.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Bailey | 2009-05-27 17:38:04 | Re: composite type and domain |
Previous Message | Grzegorz Jaśkiewicz | 2009-05-27 16:15:07 | \dt+ on 8.4 |