pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Disk Space issue
13+ messages / 9 participants
[nested] [flat]

* Disk Space issue
@ 2008-06-10 23:36 Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-10 23:55 ` Re: Disk Space issue Joshua D. Drake <jd@commandprompt.com>
  0 siblings, 1 reply; 13+ messages in thread

From: Devendra Singh Rawat @ 2008-06-10 23:36 UTC (permalink / raw)
  To: pgsql-admin

Hi,

We are using PostgreSQL 7.4.5 and facing issues with increasing disk space.

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 increase.

Suggestions on the likely problems will be appreciated.

Regards,
Devendra

**************** 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***



^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-10 23:36 Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
@ 2008-06-10 23:55 ` Joshua D. Drake <jd@commandprompt.com>
  2008-06-10 23:58   ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-11 16:11   ` Re: Disk Space issue Steve Crawford <scrawford@pinpointresearch.com>
  0 siblings, 2 replies; 13+ messages in thread

From: Joshua D. Drake @ 2008-06-10 23:55 UTC (permalink / raw)
  To: Devendra Singh Rawat <Devendra_Rawat@infosys.com>; +Cc: pgsql-admin



On Wed, 2008-06-11 at 09:36 +1000, Devendra Singh Rawat wrote:
> Hi,
> 
> We are using PostgreSQL 7.4.5 and facing issues with increasing disk space.
> 
> 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 increase.
> 
> Suggestions on the likely problems will be appreciated.

You are likely not vacuuming nearly enough.

I would also suggest strongly you update to the latest 7.4 dot release.

Joshua D. Drake

> 
> Regards,
> Devendra
> 
> **************** 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***
> 




^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-10 23:36 Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-10 23:55 ` Re: Disk Space issue Joshua D. Drake <jd@commandprompt.com>
@ 2008-06-10 23:58   ` Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-11 00:05     ` Re: Disk Space issue Joshua D. Drake <jd@commandprompt.com>
  1 sibling, 1 reply; 13+ messages in thread

From: Devendra Singh Rawat @ 2008-06-10 23:58 UTC (permalink / raw)
  To: Joshua D. Drake <jd@commandprompt.com>; +Cc: pgsql-admin

Hi Joshua,

We used Vacuum Full but were not successful. The reclaimed disk space was only few MB.
I did not get to which version I need to update my Postgres.

Regards,
Devendra

Devendra Singh Rawat
Infosys Technologies Ltd.
Tel:  +61 3 9860 2276 (D)
Fax: +61 3 9860 2501
Email: devendra_rawat@infosys.com
www.infosys.com
Powered by Intellect
         Driven by Values


-----Original Message-----
From: Joshua D. Drake [mailto:jd@commandprompt.com]
Sent: Wednesday, 11 June 2008 9:55 AM
To: Devendra Singh Rawat
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Disk Space issue



On Wed, 2008-06-11 at 09:36 +1000, Devendra Singh Rawat wrote:
> Hi,
>
> We are using PostgreSQL 7.4.5 and facing issues with increasing disk space.
>
> 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 increase.
>
> Suggestions on the likely problems will be appreciated.

You are likely not vacuuming nearly enough.

I would also suggest strongly you update to the latest 7.4 dot release.

Joshua D. Drake

>
> Regards,
> Devendra
>
> **************** 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***
>




^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-10 23:36 Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-10 23:55 ` Re: Disk Space issue Joshua D. Drake <jd@commandprompt.com>
  2008-06-10 23:58   ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
@ 2008-06-11 00:05     ` Joshua D. Drake <jd@commandprompt.com>
  2008-06-11 01:08       ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  0 siblings, 1 reply; 13+ messages in thread

From: Joshua D. Drake @ 2008-06-11 00:05 UTC (permalink / raw)
  To: Devendra Singh Rawat <Devendra_Rawat@infosys.com>; +Cc: pgsql-admin



On Wed, 2008-06-11 at 09:58 +1000, Devendra Singh Rawat wrote:
> Hi Joshua,
> 
> We used Vacuum Full but were not successful. The reclaimed disk space was only few MB.
> I did not get to which version I need to update my Postgres.

VACUUM FULL may not reclaim your index space if it bloated out. What you
are best to look at is the type of queries are being run. Determine what
is getting bloated and look at modifying how you maintain that relation.

7.4.19 (which hits soon)

Joshua D. Drake


> 
> Regards,
> Devendra
> 
> Devendra Singh Rawat
> Infosys Technologies Ltd.
> Tel:  +61 3 9860 2276 (D)
> Fax: +61 3 9860 2501
> Email: devendra_rawat@infosys.com
> www.infosys.com
> Powered by Intellect
>          Driven by Values
> 
> 
> -----Original Message-----
> From: Joshua D. Drake [mailto:jd@commandprompt.com]
> Sent: Wednesday, 11 June 2008 9:55 AM
> To: Devendra Singh Rawat
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Disk Space issue
> 
> 
> 
> On Wed, 2008-06-11 at 09:36 +1000, Devendra Singh Rawat wrote:
> > Hi,
> >
> > We are using PostgreSQL 7.4.5 and facing issues with increasing disk space.
> >
> > 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 increase.
> >
> > Suggestions on the likely problems will be appreciated.
> 
> You are likely not vacuuming nearly enough.
> 
> I would also suggest strongly you update to the latest 7.4 dot release.
> 
> Joshua D. Drake
> 
> >
> > Regards,
> > Devendra
> >
> > **************** 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***
> >
> 
> 




^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-10 23:36 Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-10 23:55 ` Re: Disk Space issue Joshua D. Drake <jd@commandprompt.com>
  2008-06-10 23:58   ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-11 00:05     ` Re: Disk Space issue Joshua D. Drake <jd@commandprompt.com>
@ 2008-06-11 01:08       ` Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-11 01:28         ` Re: Disk Space issue Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 13+ messages in thread

From: Devendra Singh Rawat @ 2008-06-11 01:08 UTC (permalink / raw)
  To: Joshua D. Drake <jd@commandprompt.com>; +Cc: pgsql-admin

We ran the SQL to get the table which are consuming maximum space.
The results are as shown:-
SELECT relname, relpages FROM pg_class ORDER BY relpages DESC;
                     relname                      | relpages
--------------------------------------------------+----------
 <table-1>                                       |    52869
 <table-2>                                       |    31267
 <table-3>                                |    15418
 <table-4>                                |     9693
 <table-5>                                    |     6426


But these only cover around few GB of data.

Regards,
Devendra

-----Original Message-----
From: Joshua D. Drake [mailto:jd@commandprompt.com]
Sent: Wednesday, 11 June 2008 10:06 AM
To: Devendra Singh Rawat
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Disk Space issue



On Wed, 2008-06-11 at 09:58 +1000, Devendra Singh Rawat wrote:
> Hi Joshua,
>
> We used Vacuum Full but were not successful. The reclaimed disk space was only few MB.
> I did not get to which version I need to update my Postgres.

VACUUM FULL may not reclaim your index space if it bloated out. What you
are best to look at is the type of queries are being run. Determine what
is getting bloated and look at modifying how you maintain that relation.

7.4.19 (which hits soon)

Joshua D. Drake


>
> Regards,
> Devendra
>
> Devendra Singh Rawat
> Infosys Technologies Ltd.
> Tel:  +61 3 9860 2276 (D)
> Fax: +61 3 9860 2501
> Email: devendra_rawat@infosys.com
> www.infosys.com
> Powered by Intellect
>          Driven by Values
>
>
> -----Original Message-----
> From: Joshua D. Drake [mailto:jd@commandprompt.com]
> Sent: Wednesday, 11 June 2008 9:55 AM
> To: Devendra Singh Rawat
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Disk Space issue
>
>
>
> On Wed, 2008-06-11 at 09:36 +1000, Devendra Singh Rawat wrote:
> > Hi,
> >
> > We are using PostgreSQL 7.4.5 and facing issues with increasing disk space.
> >
> > 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 increase.
> >
> > Suggestions on the likely problems will be appreciated.
>
> You are likely not vacuuming nearly enough.
>
> I would also suggest strongly you update to the latest 7.4 dot release.
>
> Joshua D. Drake
>
> >
> > Regards,
> > Devendra
> >
> > **************** 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***
> >
>
>




^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-10 23:36 Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-10 23:55 ` Re: Disk Space issue Joshua D. Drake <jd@commandprompt.com>
  2008-06-10 23:58   ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-11 00:05     ` Re: Disk Space issue Joshua D. Drake <jd@commandprompt.com>
  2008-06-11 01:08       ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
@ 2008-06-11 01:28         ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 13+ messages in thread

From: Tom Lane @ 2008-06-11 01:28 UTC (permalink / raw)
  To: Devendra Singh Rawat <Devendra_Rawat@infosys.com>; +Cc: Joshua D. Drake <jd@commandprompt.com>; pgsql-admin

Devendra Singh Rawat <Devendra_Rawat@infosys.com> writes:
> We ran the SQL to get the table which are consuming maximum space.
> The results are as shown:-
> SELECT relname, relpages FROM pg_class ORDER BY relpages DESC;
>                      relname                      | relpages
> --------------------------------------------------+----------
>  <table-1>                                       |    52869
>  <table-2>                                       |    31267
>  <table-3>                                |    15418
>  <table-4>                                |     9693
>  <table-5>                                    |     6426


> But these only cover around few GB of data.

pg_class.relpages is only up-to-date as of the last VACUUM.
There's already good reason to suspect that you're not vacuuming
enough; maybe some big tables are not getting vacuumed at all.

I'd suggest having a look into the data directory to see for yourself
which are the big files.  The documentation might help you:
http://www.postgresql.org/docs/8.3/static/storage.html
(IIRC, all of this except the material on tablespaces will apply
to 7.4.)

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-10 23:36 Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-10 23:55 ` Re: Disk Space issue Joshua D. Drake <jd@commandprompt.com>
@ 2008-06-11 16:11   ` Steve Crawford <scrawford@pinpointresearch.com>
  1 sibling, 0 replies; 13+ messages in thread

From: Steve Crawford @ 2008-06-11 16:11 UTC (permalink / raw)
  To: Joshua D. Drake <jd@commandprompt.com>; +Cc: Devendra Singh Rawat <Devendra_Rawat@infosys.com>; pgsql-admin

Joshua D. Drake wrote:
> On Wed, 2008-06-11 at 09:36 +1000, Devendra Singh Rawat wrote:
>   
>> Hi,
>>
>> We are using PostgreSQL 7.4.5 and facing issues with increasing disk space....
>>
>>     
> ...I would also suggest strongly you update to the latest 7.4 dot release.
>   

But as always read all the release notes between your current and your 
intended version. Usually all that is required for maintenance upgrades 
is installing new binaries but you can't assume that is always the case. 
For the 7.4 series, pay special attention to the notes for 7.4.8 and 7.4.11:

http://www.postgresql.org/docs/7.4/static/release-7-4-8.html
http://www.postgresql.org/docs/7.4/static/release-7-4-11.html

Since it sounds like you are doing lots of dump and restore, these 
issues may not be problematic for you. If possible in your situation, 
updating to the latest version (8.3.1) is preferable.

Cheers,
Steve




^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
@ 2008-06-11 06:14 Praveen Kumar (TUV) <praveen.k@renaissance-it.com>
  2008-06-11 07:42 ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  0 siblings, 1 reply; 13+ messages in thread

From: Praveen Kumar \(TUV\) @ 2008-06-11 06:14 UTC (permalink / raw)
  To: Devendra Singh Rawat <Devendra_Rawat@infosys.com>; pgsql-admin

Hi,
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.

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Devendra Singh
Rawat
Sent: Wednesday, June 11, 2008 5:07 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Disk Space issue

Hi,

We are using PostgreSQL 7.4.5 and facing issues with increasing disk
space.

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
increase.

Suggestions on the likely problems will be appreciated.

Regards,
Devendra

**************** 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@postgresql.org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-11 06:14 Re: Disk Space issue Praveen Kumar (TUV) <praveen.k@renaissance-it.com>
@ 2008-06-11 07:42 ` Devendra Singh Rawat <Devendra_Rawat@infosys.com>
  2008-06-11 07:54   ` Re: Disk Space issue Michael Monnerie <michael.monnerie@is.it-management.at>
  2008-06-11 08:19   ` Re: Disk Space issue Pavan Deolasee <pavan.deolasee@gmail.com>
  2008-06-11 08:57   ` Re: Disk Space issue Tommy Gildseth <tommy.gildseth@usit.uio.no>
  2008-06-11 14:04   ` Re: Disk Space issue Scott Marlowe <scott.marlowe@gmail.com>
  0 siblings, 4 replies; 13+ messages in thread

From: Devendra Singh Rawat @ 2008-06-11 07:42 UTC (permalink / raw)
  To: Praveen Kumar (TUV) <praveen.k@renaissance-it.com>; tgl@sss.pgh.pa.us <tgl@sss.pgh.pa.us>; Joshua D. Drake <jd@commandprompt.com>; +Cc: pgsql-admin

Hi All,

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

Regards,
Devendra

-----Original Message-----
From: Praveen Kumar (TUV) [mailto:praveen.k@renaissance-it.com]
Sent: Wednesday, 11 June 2008 4:15 PM
To: Devendra Singh Rawat; pgsql-admin@postgresql.org
Subject: RE: [ADMIN] Disk Space issue

Hi,
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.

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Devendra Singh
Rawat
Sent: Wednesday, June 11, 2008 5:07 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Disk Space issue

Hi,

We are using PostgreSQL 7.4.5 and facing issues with increasing disk
space.

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
increase.

Suggestions on the likely problems will be appreciated.

Regards,
Devendra

**************** 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@postgresql.org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-11 06:14 Re: Disk Space issue Praveen Kumar (TUV) <praveen.k@renaissance-it.com>
  2008-06-11 07:42 ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
@ 2008-06-11 07:54   ` Michael Monnerie <michael.monnerie@is.it-management.at>
  3 siblings, 0 replies; 13+ messages in thread

From: Michael Monnerie @ 2008-06-11 07:54 UTC (permalink / raw)
  To: pgsql-admin

On Mittwoch, 11. Juni 2008 Devendra Singh Rawat wrote:
> 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

And after VACUUM FULL, is it small again? Maybe you need to run it 2-3 
times a day, for your specific workload.

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: www.keyserver.net                   Key-ID: 1C1209B4

Attachments:

  signature.asc (application/pgp-signature, 193B) download

^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-11 06:14 Re: Disk Space issue Praveen Kumar (TUV) <praveen.k@renaissance-it.com>
  2008-06-11 07:42 ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
@ 2008-06-11 08:19   ` Pavan Deolasee <pavan.deolasee@gmail.com>
  3 siblings, 0 replies; 13+ messages in thread

From: Pavan Deolasee @ 2008-06-11 08:19 UTC (permalink / raw)
  To: Devendra Singh Rawat <Devendra_Rawat@infosys.com>; +Cc: Praveen Kumar (TUV) <praveen.k@renaissance-it.com>; tgl@sss.pgh.pa.us <tgl@sss.pgh.pa.us>; Joshua D. Drake <jd@commandprompt.com>; pgsql-admin

On Wed, Jun 11, 2008 at 1:12 PM, Devendra Singh Rawat
<Devendra_Rawat@infosys.com> wrote:
> Hi All,
>
> 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).
>

Check if you have autovacuum enabled and configured properly. Btw, you
should seriously consider upgrading to newer release like 8.3 which
significantly improves performance for high UPDATE work load.

Thanks,
Pavan

-- 
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com



^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-11 06:14 Re: Disk Space issue Praveen Kumar (TUV) <praveen.k@renaissance-it.com>
  2008-06-11 07:42 ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
@ 2008-06-11 08:57   ` Tommy Gildseth <tommy.gildseth@usit.uio.no>
  3 siblings, 0 replies; 13+ messages in thread

From: Tommy Gildseth @ 2008-06-11 08:57 UTC (permalink / raw)
  To: pgsql-admin; +Cc: Devendra Singh Rawat <Devendra_Rawat@infosys.com>

Devendra Singh Rawat wrote:
> Hi All,
> 
> 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.


This is a typical case where you can experience a good deal of index 
bloat. I would recommend installing the dbsize contrib module, and 
monitor the size of the relations (tables and indexes) in your database, 
to see which relations in particular is growing rapidly in size.
Once you've identified the culprit, you could use reindex or cluster to 
reclaim the dead space.
Note that reindex and cluster require fairly extensive locks, so not so 
good to use on a busy database during working hours.


-- 
Tommy Gildseth




^ permalink  raw  reply  [nested|flat] 13+ messages in thread

* Re: Disk Space issue
  2008-06-11 06:14 Re: Disk Space issue Praveen Kumar (TUV) <praveen.k@renaissance-it.com>
  2008-06-11 07:42 ` Re: Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
@ 2008-06-11 14:04   ` Scott Marlowe <scott.marlowe@gmail.com>
  3 siblings, 0 replies; 13+ messages in thread

From: Scott Marlowe @ 2008-06-11 14:04 UTC (permalink / raw)
  To: Devendra Singh Rawat <Devendra_Rawat@infosys.com>; +Cc: Praveen Kumar (TUV) <praveen.k@renaissance-it.com>; tgl@sss.pgh.pa.us <tgl@sss.pgh.pa.us>; Joshua D. Drake <jd@commandprompt.com>; pgsql-admin

On Wed, Jun 11, 2008 at 1:42 AM, Devendra Singh Rawat
<Devendra_Rawat@infosys.com> wrote:
> Hi All,
>
> 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.

Note that 7.4 was pretty poor at recovering space from the catalogs
and the associated indexes.  It could be that you would need to shut
down each night and vacuum full the catalogs in single user mode to
recover the space.

But it's been a while since I ran something older than 8.1 or so, so
it might have been an even older version that had those issues.



^ permalink  raw  reply  [nested|flat] 13+ messages in thread


end of thread, other threads:[~2008-06-11 16:11 UTC | newest]

Thread overview: 13+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-06-10 23:36 Disk Space issue Devendra Singh Rawat <Devendra_Rawat@infosys.com>
2008-06-10 23:55 ` Joshua D. Drake <jd@commandprompt.com>
2008-06-10 23:58   ` Devendra Singh Rawat <Devendra_Rawat@infosys.com>
2008-06-11 00:05     ` Joshua D. Drake <jd@commandprompt.com>
2008-06-11 01:08       ` Devendra Singh Rawat <Devendra_Rawat@infosys.com>
2008-06-11 01:28         ` Tom Lane <tgl@sss.pgh.pa.us>
2008-06-11 16:11   ` Steve Crawford <scrawford@pinpointresearch.com>
2008-06-11 06:14 Re: Disk Space issue Praveen Kumar (TUV) <praveen.k@renaissance-it.com>
2008-06-11 07:42 ` Devendra Singh Rawat <Devendra_Rawat@infosys.com>
2008-06-11 07:54   ` Michael Monnerie <michael.monnerie@is.it-management.at>
2008-06-11 08:19   ` Pavan Deolasee <pavan.deolasee@gmail.com>
2008-06-11 08:57   ` Tommy Gildseth <tommy.gildseth@usit.uio.no>
2008-06-11 14:04   ` Scott Marlowe <scott.marlowe@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox