Patrick Welche wrote:
>
> > And how shall it dsitinguish between a path and a variable?
> > > setenv PGDATA2 /home/postgres/data
> > > initlocation PGDATA2
> > And how shall it distinguish between a path and a variable?
> > But this could mean the path PGDATA2 too, couldn't it?
I test that the argument, when translated, has a non-empty result. If it
doesn't, I assume that it is an actual path.
> initlocation $PGDATA2
Yes, that's how it has always worked. I wanted it to also function
correctly when invoked with the environment variable as an argument (if
someone forgets to put in the "dollar sign").
I have a working version committed to the cvs tree which uses printenv
to extract the contents of the argument. It correctly distinguishes
between paths and envars, and does the right thing with both.
I'd appreciate any reports of problems on any platforms or environments.
Thanks all for the tips.
- Tom