Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id ECE332E004A for ; Mon, 26 May 2008 17:26:35 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 90007-02 for ; Mon, 26 May 2008 17:26:21 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by developer.postgresql.org (Postfix) with ESMTP id 5CE512E0070 for ; Mon, 26 May 2008 17:26:23 -0300 (ADT) thread-index: Aci/bt2uaLCm6tWeSciyXR52SuTUvQ== Received: from [87.127.95.195] ([87.127.95.195]) by mail01.enterprisedb.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 26 May 2008 16:27:06 -0400 Message-ID: <483B1CE7.9030201@enterprisedb.com> Date: Mon, 26 May 2008 21:26:15 +0100 Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133 From: "Heikki Linnakangas" Organization: EnterpriseDB User-Agent: Mozilla-Thunderbird 2.0.0.12 (X11/20080420) MIME-Version: 1.0 To: "Tino Wildenhain" Cc: "Campbell, Lance" , "Tom Lane" , Subject: Re: Symbolic Links to Tablespaces References: <21505.1211814531@sss.pgh.pa.us> <483B00C3.5030005@enterprisedb.com> <483B0D27.8070100@wildenhain.de> In-Reply-To: <483B0D27.8070100@wildenhain.de> Content-Type: text/plain; format=flowed; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 May 2008 20:27:06.0578 (UTC) FILETIME=[DDA27B20:01C8BF6E] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/340 X-Sequence-Number: 30308 Tino Wildenhain wrote: > Heikki Linnakangas wrote: > ... >> Shut down the database server, replace the symbolic link in >> data/pg_tblspc to the new location, and start the server again. The >> location is also stored in pg_tablespace catalog; you'll need to fix >> it with "UPDATE pg_tablespace SET spclocation ='/someotherdir/xyz_tbl' >> WHERE spcname='xyz_tbl'", or pg_dumpall will still show the old location. >> > wouldn't alter tablespace be not more easy and less fragile? Yes. But it requires copying all the data. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com