>>>How about an environment variable that points to a .pgpass type file.
>>
>>You can do that today: point $HOME at some temp directory or other.
>>AFAIR pg_dump doesn't make any other use of $HOME ...
>>
>>>Or we could even play games with PGPASSWORD - if it names an 
>existing file 
>>>that satisfies the .pgpass criteria then it will be taken as the 
>>>location of the .pgpass file instead of $HOME/.pgpass - 
>otherwise its 
>>>value will be considered to be the password itself.
>>>    
>>>
>>
>>Gaack... if you want a separate variable, we can talk about that, but
>>let's not overload PGPASSWORD like that.  Consider even just the
>>implications of whether libpq error messages should echo back the
>>"filename" ...
>>
>
>Yeah. as usual you're right :-)
>
>So let's go woth PGPASSFILE

How about --pwfile on the commandline, the same way initdb does it?

//Magnus

Thu, 19 Aug 2004 08:44:50 +0200
"Magnus Hagander" <mha@sollentuna.net>
Re: PGPASSWORD and client tools
Magnus Hagander said:
>>>>How about an environment variable that points to a .pgpass type file.

>>
>>So let's go woth PGPASSFILE
>
> How about --pwfile on the commandline, the same way initdb does it?
>

Then you can't make it part of libpq - you would have to build it into every
program that needs it.

cheers

andrew



Thu, 19 Aug 2004 07:21:29 -0400 (EDT)
"Andrew Dunstan" <andrew@dunslane.net>
Re: PGPASSWORD and client tools