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 0BE6D9DC9B0 for ; Tue, 28 Mar 2006 14:32:34 -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 27909-02 for ; Tue, 28 Mar 2006 14:32:31 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 92E8E9DC848 for ; Tue, 28 Mar 2006 14:32:28 -0400 (AST) Received: by noel.decibel.org (Postfix, from userid 1001) id E12D756423; Tue, 28 Mar 2006 12:32:28 -0600 (CST) Received: (hashcash-sendmail, from uid 1001); Tue, 28 Mar 2006 12:32:28 -0600 Date: Tue, 28 Mar 2006 12:32:28 -0600 From: "Jim C. Nasby" To: Mark Liberman Cc: pgsql-admin@postgresql.org Subject: Re: Feedback on auto-pruning approach Message-ID: <20060328183228.GV75181@pervasive.com> References: <9D938282F8C6EE43B748B910386DE93E0138B41A@srvgpimail1.GPI.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9D938282F8C6EE43B748B910386DE93E0138B41A@srvgpimail1.GPI.local> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060328:mliberman@mixedsignals.com::g/GvIwOwkOCeagZi:00000000000 0000000000000000000000002VeC X-Hashcash: 1:20:060328:pgsql-admin@postgresql.org::sjLtynXLd5C1eDol:00000000000 0000000000000000000000001EKZ X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.108 required=5 tests=[AWL=0.108] X-Spam-Score: 0.108 X-Spam-Level: X-Archive-Number: 200603/317 X-Sequence-Number: 21074 On Tue, Mar 28, 2006 at 10:23:45AM -0800, 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? Keep an eye on $PGDATA/base/{database_oid}/pgsql_tmp. > > 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. You might want to take a look at http://rrs.decibel.org, which is something I created for a similar purpose. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461