Internal fragmentations statistics Was: VACUUM FULL memory requirements - Mailing list pgsql-admin

From Evan Rempel
Subject Internal fragmentations statistics Was: VACUUM FULL memory requirements
Date
Msg-id 4B26C48F.4030501@uvic.ca
Whole thread Raw
In response to Re: VACUUM FULL memory requirements  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Internal fragmentations statistics Was: VACUUM FULL memory requirements  (Guillaume Lelarge <guillaume@lelarge.info>)
List 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

pgsql-admin by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: VACUUM FULL memory requirements
Next
From: "Net Tree Inc."
Date:
Subject: how to Stop(shutdown) specific database