From: | Josh Rovero <rovero(at)sonalysts(dot)com> |
---|---|
To: | Peter Meszaros <pme(at)prolan(dot)hu> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: database size growing continously |
Date: | 2009-10-29 15:33:25 |
Message-ID: | 1256830405.14991.25.camel@jetstream.sonalysts.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, 2009-10-29 at 15:44 +0100, Peter Meszaros wrote:
> Hi All,
>
> I use postgresql 8.3.7 as a huge queue. There is a very simple table
> with six columns and two indices, and about 6 million records are
> written into it in every day continously commited every 10 seconds from
> 8 clients. The table stores approximately 120 million records, because a
> cron job daily deletes those ones are older than 20 day. Autovacuum is
> on and every settings is the factory default except some unrelated ones
> (listen address, authorization). But my database is growing,
> characteristically ~600MByte/day, but sometimes much slower (eg. 10MB,
> or even 0!!!).
Do you ever "vacuum full" to reclaim empty record space?
--
P.J. "Josh" Rovero Vice President Sonalysts, Inc.
Email: rovero(at)sonalysts(dot)com www.sonalysts.com 215 Parkway North
Work: (860)326-3671 Waterford, CT 06385
From | Date | Subject | |
---|---|---|---|
Next Message | Ludwik Dylag | 2009-10-29 15:33:50 | Re: database size growing continously |
Previous Message | Bob Lunney | 2009-10-29 15:24:17 | Re: sub-select in IN clause results in sequential scan |