From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Re: tables, where |
Date: | 2001-03-29 18:10:49 |
Message-ID: | Pine.LNX.4.30.0103291008480.31443-100000@salmo.appl-ecosys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 29 Mar 2001, Mitch Vincent wrote:
> I'm confused as to how this could work.. The PGDATA environment variable
> (as I understand it) is used so that you don't need to supply a -D <data
> dir> argument to the postmaster at startup. If you had PGDATA and PGDATA2
> defined, how does the backend know which to use at startup without
> specifying something on the command line -- and if you're putting something
> on the command line anyway, why not just say -D <other data dir> ?
Mitch,
I no longer remember the specific syntax, but the -D wasn't working
whether or not another directory was specified as an environment variable.
In other words, only the default data directory would be seen as valid by
postgres. What I'm asking is if this has now been changed.
Thanks,
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard(at)appl-ecosys(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2001-03-29 18:12:03 | Re: tables, where |
Previous Message | Soma Interesting | 2001-03-29 17:51:54 | Re: timestamp/function question |