From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | Jan Otto <asche(at)me(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rainer Bauer <usenet(at)munnin(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Space for pg_dump |
Date: | 2009-05-14 06:29:00 |
Message-ID: | alpine.GSO.2.01.0905140200140.17861@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 20 Apr 2009, Jan Otto wrote:
> If you have big toast tables you get wrong results with the query suggested
> at http://wiki.postgresql.org/wiki/Disk_Usage because it takes the toasted
> values not into account.
I can't recall why I wrote that to filter out things in the pg_toast
namespace in the first place. I just took the easy way out here--the
query has been updated to not exclude relations in that namespace anymore
and I link to the TOAST docs for more details.
I consider combining all the values together, as you did in your example
code and as pg_total_relation_size does, as a different type of report.
Accordingly, I just updated with examples of both types, as well as
something to work against pre-8.1 databases.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Philipp Marek | 2009-05-14 06:31:20 | Re: Btree indizes, FILLFACTOR, vacuum_freeze_min_age and CLUSTER |
Previous Message | Richard Huxton | 2009-05-14 06:16:34 | Re: Connections Crashing |