X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id B2FE2D1F001 for ; Tue, 20 Apr 2004 21:24:53 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 81108-04 for ; Tue, 20 Apr 2004 21:24:53 -0300 (ADT) Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by svr1.postgresql.org (Postfix) with ESMTP id 4B8E2D1EFB7 for ; Tue, 20 Apr 2004 21:24:50 -0300 (ADT) Received: from commandprompt.com (clbb-248.saw.net [64.146.135.248]) (authenticated) by hosting.commandprompt.com (8.11.6/8.11.6) with ESMTP id i3L0Oou25853; Tue, 20 Apr 2004 17:24:51 -0700 Message-ID: <4085BFF0.4050604@commandprompt.com> Date: Tue, 20 Apr 2004 17:27:28 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Anjan Dave Cc: pgsql-performance@postgresql.org Subject: Re: Moving postgres to FC disks References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509814D@vt-pe2550-001.vantage.vantage.com> In-Reply-To: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509814D@vt-pe2550-001.vantage.vantage.com> Content-Type: multipart/alternative; boundary="------------030009030401050901060103" X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.7 tagged_above=0.0 required=5.0 tests=HTML_50_60, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: X-Archive-Number: 200404/313 X-Sequence-Number: 6613 This is a multi-part message in MIME format. --------------030009030401050901060103 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit > -With the db size being as big as, say, 30+GB, how do I move it on the > new logical drive? (stop postgresql, and simply move it over somehow > and make a link?) > I would stop the database, move the data directory to the new volume using rsync then start up postgresql pointed at the new data directory. Providing everything is working correctly you can then remove the old data directory. > -Currently, the internal RAID volume is ext3 filesystem. Any > recommendations for the filesystem on the new FC volume? Rieserfs? > > > XFS > DBs are 7.4.1(RH9), and 7.2.3 (RH8). > > > > > > Appreciate any pointers. > > > > Thanks, > Anjan > -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL --------------030009030401050901060103 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

-With the db size being as big as, say, 30+GB, how do I move it on the new logical drive? (stop postgresql, and simply move it over somehow and make a link?)

I would stop the database, move the data directory to the new volume using rsync then start up postgresql pointed at the new data directory.
Providing everything is working correctly you can then remove the old data directory.

-Currently, the internal RAID volume is ext3 filesystem. Any recommendations for the filesystem on the new FC volume? Rieserfs?

 

XFS

DBs are 7.4.1(RH9), and 7.2.3 (RH8).

 

 

Appreciate any pointers.

 

Thanks,
Anjan



-- 
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
--------------030009030401050901060103--