X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A0CEB3CAFD1 for ; Fri, 17 Dec 2004 02:00:49 +0000 (GMT) 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 97095-09 for ; Fri, 17 Dec 2004 02:00:43 +0000 (GMT) Received: from millenium.mst.co.jp (unknown [210.230.185.241]) by svr1.postgresql.org (Postfix) with ESMTP id C9F6F3CAF14 for ; Fri, 17 Dec 2004 02:00:43 +0000 (GMT) Received: from mst1x5r347kymb (lc12114 [192.168.1.114]) by millenium.mst.co.jp (8.11.6p2/3.7W) with SMTP id iBH20gZ06921 for ; Fri, 17 Dec 2004 11:00:42 +0900 Message-ID: <00c701c4e3dc$7da40cf0$7201a8c0@mst1x5r347kymb> From: "Iain" To: References: <20041216180246.54806.qmail@web12701.mail.yahoo.com> Subject: Re: easy one: location of the database cluster Date: Fri, 17 Dec 2004 11:02:35 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200412/192 X-Sequence-Number: 15778 Hi, Looks like I should get to know the "Filesystem Hierarchy Standard" atleast a little better. >> The RPM distributions of PG use /var/lib/pgsql/data as the standard >> PGDATA value. I'm not sure what Debian does but I think it might be >> different. Also there has been some talk of including the major >> release number (7.4, 8.0, etc) in the standard PGDATA value, to ease >> migration across server versions by allowing different versions to be >> installed concurrently. > > Oh, this would be excellent! The fear of dealing with 2 different > versions and the fear of overwriting something by mistake is what's > keeping me from upgrading my PG installation. This is partly my concern also. It's only a concern for me because I don't have any direct experience of managing and upgrading production systems using packages, I have always used the source code download. Backing up your databases before an upgrade is always advisable, but on the other hand, we typically don't want to have to endure a restore just because we messed up a minor upgrade. if you are building from source it's no problem as you just don't run initdb. As to package upgrades, presumably they don't touch your data. I have to write a manual for the maintenance and updating of the server, so I'm gonna have to test it all anyway. Getting back to my original question (as I think it was) I havn't seen any reason not to use the default data directory used by the package, especially if it conforms with the above mentioned standard. Regards Iain