From: | "Iain" <iain(at)mst(dot)co(dot)jp> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | easy one: location of the database cluster |
Date: | 2004-12-16 08:55:05 |
Message-ID: | 000801c4e34c$f3572210$7201a8c0@mst1x5r347kymb |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mortimer | 2004-12-16 10:06:54 | robust way of moving tables to a different disk?? |
Previous Message | Iain | 2004-12-16 08:41:01 | Re: Tyan Thunder MB for postgres server |