Skip site navigation (1) Skip section navigation (2)

Re: Estimating Database Disk Space

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ralough(at)iee(dot)org
Cc: PostgreSQL Novice ML <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Estimating Database Disk Space
Date: 2002-03-20 21:43:21
Message-ID: 8021.1016660601@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-novice
Richard A Lough <ralough(dot)ced(at)dnet(dot)co(dot)uk> writes:
> Only one of my active databases 
> shows significant figures (recently increased): 

> relpages | relname 
> 17473	pg_attribute_relid_attnam_index
> 7267	pg_attribute_relid_attnum_index
> 3245	pg_attribute

Yipes ... you must do a lot of table creation and deletion.

The index bloat here is a known result of inefficiency in vacuuming
indexes (there's no good way to reclaim index pages at the moment).
You could probably fix it by REINDEXing pg_attribute, but it might
be easier to just dump, dropdb, createdb, reload that database.

Yes, there's a TODO item to improve index vacuuming ...

			regards, tom lane

In response to

Responses

pgsql-novice by date

Next:From: Doug SilverDate: 2002-03-20 22:14:08
Subject: perl/DBI transaction rollback of sequences
Previous:From: Richard A LoughDate: 2002-03-20 21:34:31
Subject: Re: Estimating Database Disk Space

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group