From: Iain <iain@mst.co.jp>
To: pgsql-admin@postgresql.org
Subject: easy one: location of the database cluster
Date: Thu, 16 Dec 2004 17:55:05 +0900
Message-ID: <000801c4e34c$f3572210$7201a8c0@mst1x5r347kymb> (raw)
Hi All,
I'm in the process of putting together some docs for a new postgres server.
For development use, I've always just been content to have the PGDATA
directory as a subdirectory of the main postgres install directory which is
/usr/local/pgsql/ by default (when installing from source anyway).
My question is whether there is any good reason not to do that in a
production environment (for example upgrade time)?
Is there a "standard" directory that people tend to use for this, such as
/var/local/pgsql/ ?
Even if there are no standards, I do like to follow conventions where they
exist, since I don't expect to be around by the time this system will be
requiring it's first round of maintenance ;-)
OS is (will most probably be) RHEL3
Cheers
Iain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: iain@mst.co.jp
Subject: Re: easy one: location of the database cluster
In-Reply-To: <000801c4e34c$f3572210$7201a8c0@mst1x5r347kymb>
References: <000801c4e34c$f3572210$7201a8c0@mst1x5r347kymb>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox