I recreated my database this morning with a dump size of 3GB, which after database creation occupied 3.5GB on disk.
And in less than 8 hours it has bloated to additional 3.7GB (the disk size now is 7.2GB).
There are quite a few DML operations which are happening on my DB.
SELECT relname, relpages FROM pg_class ORDER BY relpages DESC;
relname | relpages
< table1 > | 180676
< table2 > | 22828
< table3 > | 13469
< table4 > | 9174
< table5 > | 7246
< table6 > | 3865
< table7 > | 2384
< table8 > | 2013
< table9 > | 1836
< table10 > | 1356
< table11 > | 1349
< table12 > | 1025
< table13 > | 910
< table14 > | 896
< table15 > | 797
< table16 > | 708
< table17 > | 665
< table18 > | 601
< table19 > | 407
< table20 > | 374
From: Praveen Kumar (TUV) [mailto:praveen(dot)k(at)renaissance-it(dot)com]
Sent: Wednesday, 11 June 2008 4:15 PM
To: Devendra Singh Rawat; pgsql-admin(at)postgresql(dot)org
Subject: RE: [ADMIN] Disk Space issue
I think you have a lot DML operation in your database and you are not
vacuuming your database . So try to execute command vacuum analyze
<<table name >>; in your schema where you are facing problem.
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Devendra Singh
Sent: Wednesday, June 11, 2008 5:07 AM
Subject: [ADMIN] Disk Space issue
We are using PostgreSQL 7.4.5 and facing issues with increasing disk
Here is some information about our configuration.
The data dump size is around 3 GB. And it is occupying around 120GB on
the disk. When we recreate the database from data dump it takes around
3.5GB of disk space.
But the database size increases by 1 GB daily though actual data added
maybe in KB. We are not able to decipher as to what is causing this
Suggestions on the likely problems will be appreciated.
**************** CAUTION - Disclaimer ***************** This e-mail
contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the
use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further,
you are not to copy, disclose, or distribute this e-mail or its contents
to any other person and any such actions are unlawful. This e-mail may
contain viruses. Infosys has taken every reasonable precaution to
minimize this risk, but is not liable for any damage you may sustain as
a result of any virus in this e-mail. You should carry out your own
virus checks before opening the e-mail or attachment. Infosys reserves
the right to monitor and review the content of all messages sent to or
from this e-mail address. Messages sent to or from this e-mail address
may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org) To make
changes to your subscription:
In response to
pgsql-admin by date
|Next:||From: Michael Monnerie||Date: 2008-06-11 07:43:04|
|Subject: Re: Postgres security issue - protecting datafiles|
|Previous:||From: Richard Huxton||Date: 2008-06-11 07:07:28|
|Subject: Re: what gives: SELECT INVALID SELECT STATEMENT TO FORCE
ODBC DRIVER TO UNPREPARED STATE|