X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id BC28E9DCA06 for ; Tue, 28 Mar 2006 14:28:11 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 26679-04 for ; Tue, 28 Mar 2006 14:28:08 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 5822C9DCA36 for ; Tue, 28 Mar 2006 14:28:04 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Tue, 28 Mar 2006 18:28:03 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 28 Mar 2006 12:28:03 -0600 Subject: Re: Feedback on auto-pruning approach From: Scott Marlowe To: Mark Liberman Cc: pgsql-admin@postgresql.org In-Reply-To: <9D938282F8C6EE43B748B910386DE93E0138B41A@srvgpimail1.GPI.local> References: <9D938282F8C6EE43B748B910386DE93E0138B41A@srvgpimail1.GPI.local> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1143570483.3625.67.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 28 Mar 2006 12:28:03 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.142 required=5 tests=[AWL=0.141, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.142 X-Spam-Level: X-Archive-Number: 200603/316 X-Sequence-Number: 21073 On Tue, 2006-03-28 at 12:23, Mark Liberman wrote: > > Probably your biggest issue will be temporary files created by > temporary tables, sorts that spill to disk, etc. > > Is there any way to monitor this so I can estimate? > > > What I'm confused by is the concern about disk space in the first > place. > > We provide a device to customers that must run in an unattended > fashion for as long as the hardward holds up. So, regardless of the > disk size, they will run out at some time. Some of our solutions grow > by 3.5 Gigs per day - and 6 months of history is not an unreasonable > expectation. We've just decided we want to keep as much history as > possible given space limitations. If most of that is text, it should be fairly compressible. So, how compressible are the data, and have you done some very basic checks to see how much your postgresql data directory grows when you add to the database. It's pretty easy to do. Just, as the postgres user: cd $PGDATA du -sh base (load a couple gigs of data) du -sh base and compare the difference. It'll at least get you in the ball park.