...
> Agreed. Consistency argues for the postgresql.conf solution, not
> security. Also, I would like to see initlocation removed as soon as we
> get a 100% functional replacement. We have fielded too many questions
> about how to set it up.
Hmm. I'm not sure the best way to look, but I was able to find three or
four questions since 1999 on the mailing lists (used "initlocation
problem help"; most other choices got lots of false hits).
And they do seem to sometimes involve the inability to type commands or
to define environment variables. I'll avoid the snide remarks about DBAs
who don't know an envar from a hole in the wall (oops...). This day of
sarcasm is getting sort of fun. Can't wait to take a shower and move on
to a more polite tomorrow though ;)
btw, a "100% functional replacement" is escaping definition so far. The
"no envar" camp has not thought through the issues yet, though the
issues can be found in the threads. Better to decide what the
requirements are before throwing out the solution.
- Thomas
