Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 55CE09FA4A0 for ; Wed, 7 Feb 2007 04:31:12 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 69702-03 for ; Wed, 7 Feb 2007 04:31:06 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from ipmail02.adl2.internode.on.net (ipmail02.adl2.internode.on.net [203.16.214.141]) by postgresql.org (Postfix) with ESMTP id 312509FA434 for ; Wed, 7 Feb 2007 04:31:07 -0400 (AST) Received: from ppp247-71.static.internode.on.net (HELO [192.168.8.200]) ([203.122.247.71]) by ipmail02.adl2.internode.on.net with ESMTP; 07 Feb 2007 19:01:04 +1030 X-IronPort-AV: i="4.13,293,1167571800"; d="scan'208"; a="81507673:sNHT46698568" Message-ID: <45C98E48.9030509@007Marketing.com> Date: Wed, 07 Feb 2007 19:01:04 +1030 From: Shane Ambler User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: Karthikeyan Sundaram CC: smarlowe@g2switchworks.com, pgsql-admin@postgresql.org Subject: Re: how to add a new data partition References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.288 tagged_above=0 required=5 tests=AWL, BAYES_40, BIZ_TLD, SPF_HELO_PASS X-Spam-Level: * X-Archive-Number: 200702/99 X-Sequence-Number: 24564 Karthikeyan Sundaram wrote: > Hi Scott, > > Thanks for replying. The tablespace is not the main problem here. I > want the data files to grow in the new partition along with the old > linux partition. > > Let me put like this. > > We have a linux partition of 120GB called as > /local/postgres/database/Data/< followed by all files> > > This /local partition is 95 % used. > > So we are adding one more partition called /local1 which is > approximately 250 GB. Now I want to inform postgres that after /local > partiion is 100 %, I want to utilize the /local1 so that the database > can grow significantly. In other words, the data file created and > maintained by postgres will grow in the /local1 partition. The closest I would think is partitioning - data matching certain criteria can be in one tablespace and other data in another tablespace. This won't be just once this disk is full use another - you would say something like table1's rows with id<2000000 on this disk and id>=2000000 on another. If your data is that large you may want to look into the benefit's it can offer even if you do use lvm. http://www.postgresql.org/docs/current/interactive/ddl-partitioning.html -- Shane Ambler pgSQL@007Marketing.com Get Sheeky @ http://Sheeky.Biz