| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Richard J Kuhns <rjk(at)grauel(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Question about databases in alternate locations... |
| Date: | 2000-05-17 05:38:58 |
| Message-ID: | 39223072.63596770@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
> Could anyone please tell me what I'm doing wrong? I'm sure I'm just
> overlooking something, but what?
As Jeff pointed out, the environment variable "P" must be known to the
server backend to be used in the WITH LOCATION clause. Using it in the
preceeding initlocation invocation was correct. The utility tries it
as an environment variable, then as an absolute path, so "initlocation
P" and "initlocation $P" are both valid. You can make the environment
variable known to the backend by defining it in the postgres account's
.cshrc or .bashrc file, or by explicitly setting it before firing up
the backend.
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Mijaylov | 2000-05-17 06:16:33 | simple question for users and db |
| Previous Message | Tom Lane | 2000-05-17 03:35:17 | Re: 7.0 psql, readline and history. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-05-17 05:49:15 | Re: SET type (was Re: WAL versus Postgres) |
| Previous Message | Alfred Perlstein | 2000-05-17 04:36:01 | Re: Berkeley DB license |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rudolph, Michael | 2000-05-17 06:11:22 | AW: What is the difference between NULL and "undef" |
| Previous Message | Kyle Bateman | 2000-05-17 00:17:10 | question on update/delete rules on views |