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 5EBC99DC852 for ; Tue, 28 Mar 2006 14:42:21 -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 30597-01 for ; Tue, 28 Mar 2006 14:42:17 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from web31804.mail.mud.yahoo.com (web31804.mail.mud.yahoo.com [68.142.207.67]) by postgresql.org (Postfix) with SMTP id 7FD759DCAEF for ; Tue, 28 Mar 2006 14:42:14 -0400 (AST) Received: (qmail 17865 invoked by uid 60001); 28 Mar 2006 18:42:13 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=1dOyZk5RsbFPGc2hPXpjVANCF8vmjEWAmzJk05GWZYjAfAdCxWBrS41D9rRn0GXDKJ2EomAlR/fTMeZEm1P8qwHyhKHlJCnUoce21Nr6SHIlNXQBFc3w5lA7R/3JJ8sWfhTyA19nA5vbRXz7sxouX4yyf5fUwYxBmHc2p8kvsuM= ; Message-ID: <20060328184213.17863.qmail@web31804.mail.mud.yahoo.com> Received: from [63.203.180.122] by web31804.mail.mud.yahoo.com via HTTP; Tue, 28 Mar 2006 10:42:13 PST Date: Tue, 28 Mar 2006 10:42:13 -0800 (PST) From: Richard Broersma Jr Subject: Re: Feedback on auto-pruning approach To: "Jim C. Nasby" , Mark Liberman Cc: pgsql-admin@postgresql.org In-Reply-To: <20060328183228.GV75181@pervasive.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.138 required=5 tests=[AWL=-0.220, DNS_FROM_RFC_ABUSE=0.479, DNS_FROM_RFC_WHOIS=0.879] X-Spam-Score: 1.138 X-Spam-Level: * X-Archive-Number: 200603/318 X-Sequence-Number: 21075 Could RRS be implemented in a similar fashion to OPC-HDA? Regards, Richard --- "Jim C. Nasby" wrote: > 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq >