X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 97826D9C5B for ; Thu, 3 Nov 2005 21:34:30 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 78485-10 for ; Fri, 4 Nov 2005 01:34:23 +0000 (GMT) X-Greylist: delayed 03:06:47.744453 by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by svr1.postgresql.org (Postfix) with ESMTP id A1350DB879 for ; Thu, 3 Nov 2005 21:28:43 -0400 (AST) Received: from flake.decibel.org (flake.decibel.org [67.100.216.10]) by svr2.postgresql.org (Postfix) with ESMTP id D51FDF1067 for ; Thu, 3 Nov 2005 19:21:31 +0000 (GMT) Received: by flake.decibel.org (Postfix, from userid 1001) id 3CF54152A6; Thu, 3 Nov 2005 13:21:30 -0600 (CST) Date: Thu, 3 Nov 2005 13:21:30 -0600 From: "Jim C. Nasby" To: Tom Lane Cc: dave.bath@unix.net, pgsql-admin@postgresql.org Subject: Re: Pre-allocation of space: a business rationale Message-ID: <20051103192130.GT55520@pervasive.com> References: <21438.1130817553@sss.pgh.pa.us> <200511021400.05346.xzilla@users.sourceforge.net> <200511031427.10391.dave.bath@unix.net> <17603.1130989680@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17603.1130989680@sss.pgh.pa.us> X-Operating-System: FreeBSD 4.11-RELEASE-p10 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.007 required=5 tests=[AWL=0.007] X-Spam-Score: 0.007 X-Spam-Level: X-Archive-Number: 200511/36 X-Sequence-Number: 19409 On Wed, Nov 02, 2005 at 10:48:00PM -0500, Tom Lane wrote: > "Bath, David" writes: > > C) I want to avoid the possibility of uncontrolled growth of luser data > > blowing disk leading to stoppage of 24x7 data. > > You put the luser data and the critical data into separate tablespaces > that are in separate partitions (filesystems). End of problem ... > > (And no, I don't believe in having Postgres reinvent filesystem-level > functionality. If you didn't set up appropriate hard partitions, > consider a loopback filesystem for your tablespace.) Does every OS we support have a loopback filesystem? Can they all impose space limits? It doesn't seem unreasonable to support a limit on tablespace (or table) size. It also doesn't seem like it would take that much code to add support for it. Of course usual disclaimer about 'submit a patch then' applies, but it sounds like such a patch would get rejected out-of-hand. -- 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