X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 226E54758DC for ; Thu, 27 Feb 2003 07:34:30 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 00751-05 for ; Thu, 27 Feb 2003 07:34:19 -0500 (EST) Received: from contactbda.com (ipn36372-e65122.net-resource.net [216.204.66.226]) by postgresql.org (Postfix) with ESMTP id 7158F474E42 for ; Thu, 27 Feb 2003 07:34:10 -0500 (EST) Received: (from apache@localhost) by contactbda.com (8.11.2/8.11.2) id h1RCYCF13164; Thu, 27 Feb 2003 07:34:12 -0500 Date: Thu, 27 Feb 2003 07:34:12 -0500 Message-Id: <200302271234.h1RCYCF13164@contactbda.com> From: "Jim Buttafuoco" To: "Christopher Kings-Lynne" , "Tom Lane" , "Andrew Sullivan" , Reply-To: jim@contactbda.com Subject: Re: Index File growing big. In-Reply-To: <04d701c2de3f$1f241700$6500a8c0@fhp.internal> References: <20030226070040.C8814@mail.libertyrms.com> <027001c2ddfe$49274fe0$6500a8c0@fhp.internal> <9042.1046329009@sss.pgh.pa.us> X-Mailer: Open WebMail 1.53 20011216 X-OriginatingIP: 192.168.1.22 (jim) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/226 X-Sequence-Number: 1282 All, I was the person who submitted the patch. I tried to a generic syntax. I also tried to keep the tablespace concept simple. See my posting on HACKERS/GENERAL from a week or 2 ago about the syntax. I am still interested in working on this patch with others. I have many system here that are 500+ gigabytes and growing. It is a real pain to add more disk space (I have to backup, drop database(s), rebuild raid set (I am using raid 10) and reload data). Jim > > > You should note that someone already has sent in a patch for > tablespaces, it > > > hasn't been acted on though - can't quite remember why. Maybe we should > > > resurrect it... > > > > It's been awhile, but my recollection is that the patch had restricted > > functionality (which would be okay for a first cut) and it invented SQL > > syntax that seemed to lock us into that restricted functionality > > permanently (not so okay). Details are fuzzy though... > > Well, I'll resurrect it and see if it can be improved. Tablespaces seem to > be a requested feature these days... > > Chris > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster