From: | Thom Brown <thombrown(at)gmail(dot)com> |
---|---|
To: | paladine <yasinmalli(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: reducing postgresql disk space |
Date: | 2010-05-26 15:05:22 |
Message-ID: | AANLkTilMBn9CPzPBSPmT-RDFZkL3YQETb5mlIooIIEAY@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 26 May 2010 15:50, paladine <yasinmalli(at)gmail(dot)com> wrote:
>
> It is default value ( #checkpoint_segments = 3 # in logfile segments, min
> 1, 16MB each )
> Many of my database configurations are default values. (plain TOAST etc)
> my database is a log database so, some tables of db grow everytime.
> My ' /base ' directory contains a lot of compressed object (1GB size)
> These are maybe normal operations but I don't understand that
> although I delete many rows from my db and regularly vacuum , reindexing
> operations,
> how doesn't postgresql give back that deleted areas for reusing.
>
I'm just wondering if you're still building up the initial set of WAL
files which will begin to plateau if the data in your database in
roughly consistent in size over time.
Try:
select datname, pg_size_pretty(pg_database_size(datname)) from
pg_database order by datname;
That should give you the actual sizes of each database. Also, how
verbose is the database logging? If you're logging every query to a
log file that may also account for it.
Regards
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Palle Girgensohn | 2010-05-26 15:17:56 | why doesn't insert into foo delete from bar returning baz work? |
Previous Message | paladine | 2010-05-26 14:50:43 | Re: reducing postgresql disk space |