| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | l(dot)rame(at)griensu(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Database size |
| Date: | 2010-01-11 23:27:38 |
| Message-ID: | 4B4BB3EA.6070004@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/01/2010 2:00 AM, Leonardo M. Ramé wrote:
> A customer of mine asked me to periodically delete old, unneeded records
> containing ByteA fields, because he think it will reduce the database
> size on disk. Is this true?. For example, in Firebird, the database size
> is not reduced until you do a Backup-Restore of the database.
It won't shrink it unless you do a VACUUM FULL or CLUSTER, but it *will*
prevent growth or (if you're adding more data than you're deleting)
reduce the rate of growth.
Make sure autovacuum is running and (for pre-8.4 databases) your free
space map settings are sufficient.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-01-12 00:01:00 | Re: replication from multiple "master" servers to a single read-only slave |
| Previous Message | Craig Ringer | 2010-01-11 23:25:44 | Re: Using a lock to avoid: could not open relation with OID |