database size after a DELETE and VACUUM

From: Mike(dot)Samson(at)apcc(dot)com
To: pgsql-admin(at)postgresql(dot)org
Subject: database size after a DELETE and VACUUM
Date: 2005-07-01 13:30:50
Message-ID: OF10E93ADC.96387340-ON85257031.004879C3-85257031.004A3C0E@apcc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello All,

I need a reliable way to determine the overall size of our database.
Recently, I started using the database_size() function from the dbsize
contrib.

Everything seems to work great until I need to delete records.
After I DELETE records, the pg_autovacuum daemon kicks in an runs a VACUUM.

Once the VACUUM finishes, I run database_size() again and the size does not
decrease.

I would expect the database size to decrease after the VACUUM.
I also don't want to run a VACUUM FULL because this kills the performance
of the system.

Do I have any other alternatives to determine the database size reliably
after a DELETE
and a VACUUM?

Note that I have also experimented with reltuples which does not give me
accurate results
either unless I run two VACUUMS in a row.

Please help.

Thank you,
Mike Samson
Senior Software Engineer
APC

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ben Kim 2005-07-01 13:31:09 Re: restore database from bare files
Previous Message Joel Fradkin 2005-07-01 13:09:29 encoding converting from ascii to unicode