> Of course, given that most OS's don't have the 'ps' environment
problem,
> maybe we have to keep PGPASSWORD around. It is up to the group. Do
> people want me to change my wording of the option in the SGML sources?
>
> <envar>PGPASSWORD</envar>
> sets the password used if the backend demands password
> authentication. This is not recommended because the password can
> be read by others using a <command>ps</command> environment flag
> on some platforms.
I think the wording is good. I would keep supporting the envar.
What exactly speaks against a commandline switch, that gets hidden
with the postmaster argv trick, and a similar notice as for PGPASSWORD.
For me, this would be the most convenient form of supplying a password
(if I used db side passwords :-).
Andreas