From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Preferred Installation/Data Directories |
Date: | 2007-04-27 14:50:18 |
Message-ID: | Pine.LNX.4.64.0704270747310.12057@salmo.appl-ecosys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 27 Apr 2007, Tom Lane wrote:
> No, it hasn't. The PG code itself doesn't make any assumptions about the
> location of $PGDATA AFAIR, but there are a large number of packagings that
> assume specific places like /var/lib/pgsql/. If you've changed platforms
> or changed between installing from source and installing a prebuilt
> package, you might notice some variability. In any case you're certainly
> welcome to put $PGDATA anywhere you want.
Thanks, Tom. That does clear up what I've seen over the years. The
executables go in /usr/bin/ (at least they do with Slackware), but $PGDATA
is what I've seen changed between building from source and installing
packages.
> [ Thinks for a bit ... ] Note that "packaging" might extend further than
> meets the eye. For instance, if you want to move $PGDATA on a recent Red
> Hat system, you need to tweak not only the initscript but the SELinux
> policy, which by default will constrain the postmaster to write only under
> /var/lib/pgsql/.
I see in postgresql.SlackBuild where the data directories are specified.
I'll change that from /var/lib/pgsql/data to /usr/local/pgsql/data and
rebuild the package.
Very much appreciated,
Rich
--
Richard B. Shepard, Ph.D. | The Environmental Permitting
Applied Ecosystem Services, Inc. | Accelerator(TM)
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
From | Date | Subject | |
---|---|---|---|
Next Message | H.J. Sanders | 2007-04-27 15:03:09 | Re: Feature Request --- was: PostgreSQL Performance Tuning |
Previous Message | Alvaro Herrera | 2007-04-27 14:46:07 | Re: Using a library compiled for 8.3 in 8.2 |