Oliver Jowett wrote:
postgresbugs wrote:
The functionality provided by PGPASSWORD should not be removed unless
there is a functionality other than .pgpass, which is fine for some
uses and not for others, that will provide similar functionality. That
could be psql and pg_dump and the like accepting a password on the
command line as I stated earlier.
Putting the password on the command line would be even more of a
security problem than PGPASSWORD is now. I agree that an alternative to
,pgpass would be useful, but it needs to be a *secure* alternative.
The command line could take a file handle of an inherited pipe.
Regards,
Andreas
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
