| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | paladine <yasinmalli(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump-restore concurrency |
| Date: | 2010-07-22 00:57:26 |
| Message-ID: | 4C479776.3040006@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 21/07/10 20:21, paladine wrote:
>
> I have a linux daemon that parses some datas and writes to db continuously
> but my db is growing unexpectedly so I must reduce disk space once a week.
I assume you're also deleting from the database, given that its growth
is a problem.
It sounds like you need to fix your autovacuum settings. Make autovacuum
much more aggressive. This should prevent the growth, so you don't need
to do all this messing around with dumps and reloads or VACUUM FULL.
See:
http://www.postgresql.org/docs/current/static/routine-vacuuming.html#AUTOVACUUM
http://wiki.postgresql.org/wiki/Introduction_to_VACUUM,_ANALYZE,_EXPLAIN,_and_COUNT
http://wiki.postgresql.org/wiki/VACUUM_FULL
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2010-07-22 03:02:19 | Re: Bitmask trickiness |
| Previous Message | Howard Rogers | 2010-07-21 21:58:03 | Re: Bitmask trickiness |