Internal fragmentations statistics Was: VACUUM FULL memory requirements

From: Evan Rempel <erempel(at)uvic(dot)ca>
To:
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Internal fragmentations statistics Was: VACUUM FULL memory requirements
Date: 2009-12-14 23:04:47
Message-ID: 4B26C48F.4030501@uvic.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


Is there a command/tool that will report on how FULL a table is getting?
If there is, how intrusive is it? How computationally heavy is it?

We have a database that is approx 100 million rows with
approx 2 million insert/updates per day. Each day old data
is purged from the database. The end result is a mostly static
footprint with regards to disk space used, but I would like to
know how much room is usable inside the tables as well as the
OS file system (that part is easy).

--
Evan Rempel

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Net Tree Inc. 2009-12-15 03:32:49 how to Stop(shutdown) specific database
Previous Message Kevin Grittner 2009-12-14 21:54:57 Re: VACUUM FULL memory requirements