| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bob Parkinson <rwp(at)biome(dot)ac(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: alternative DB locations |
| Date: | 2000-10-03 14:39:40 |
| Message-ID: | 17655.970583980@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bob Parkinson <rwp(at)biome(dot)ac(dot)uk> writes:
omni.ac.uk> export PGDATA2=/public_searchable_0
omni.ac.uk> initlocation PGDATA2
...
omni.ac.uk> createdb 'testdb' -D 'PGDATA2'
> ERROR: The database path 'PGDATA2' is invalid. This may be due to a
> character that is not allowed or because the chosen path isn't permitted
> for databases
The backend will not take 'PGDATA2' as a location unless that
environment variable exists in the *postmaster's* environment.
Creating it in the client's environment won't do (except for
initlocation, which is only a shell script).
Don't forget to modify your startup scripts so that PGDATA2
is established for the postmaster on future restarts, too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Hoffmann | 2000-10-03 14:44:31 | Re: alternative DB locations |
| Previous Message | Tom Lane | 2000-10-03 14:36:20 | Re: trouble with trigger/function??? |