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 19B079DC9DD for ; Tue, 28 Mar 2006 14:19:09 -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 24537-03 for ; Tue, 28 Mar 2006 14:19:06 -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 E7E769DC9BC for ; Tue, 28 Mar 2006 14:19:04 -0400 (AST) Received: by noel.decibel.org (Postfix, from userid 1001) id CF7D556423; Tue, 28 Mar 2006 12:19:04 -0600 (CST) Received: (hashcash-sendmail, from uid 1001); Tue, 28 Mar 2006 12:19:04 -0600 Date: Tue, 28 Mar 2006 12:19:03 -0600 From: "Jim C. Nasby" To: Mark Liberman Cc: pgsql-admin@postgresql.org Subject: Re: Feedback on auto-pruning approach Message-ID: <20060328181903.GU75181@pervasive.com> References: <9D938282F8C6EE43B748B910386DE93E0138B418@srvgpimail1.GPI.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9D938282F8C6EE43B748B910386DE93E0138B418@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::cRxANxVaowxRIq4e:00000000000 0000000000000000000000002p0p X-Hashcash: 1:20:060328:pgsql-admin@postgresql.org::oE5M6Ngvjw5oO440:00000000000 00000000000000000000000066kk 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/313 X-Sequence-Number: 21070 On Mon, Mar 27, 2006 at 06:32:42PM -0800, Mark Liberman wrote: > So, I have finally complete this auto-pruning solution. It has proven effective in keeping the size of the db under whichever threshold I set in an unattended fashion. > > I have one final question. If my goal is to maximize the amount of historical data that we can keep - e.g. set the db size limit to be as large as possible - how much disk space should I reserve for standard Postgres operations - e.g. sort space, WAL, etc.. I'm sure this depends a bit on our configuration, etc.. but if someone can point me in the direction as to what factors I should consider, I'd greatly appreciate it. Probably your biggest issue will be temporary files created by temporary tables, sorts that spill to disk, etc. What I'm confused by is the concern about disk space in the first place. Drives are very cheap, people are normally much more concerned about IO bandwidth. -- 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