Hi Dennis, all.
You are right. I know that sounds stupid, but the problem why the
environment variable didn't work was due that 'P' :). I don't know why but I
didn't realize that I was writing the name of the variable wrong :S
Now, I've tried both options and both works correctly. I think for the
moment will continue with the environment variable way. I only create it
while executing a .bat file for creating the database and create the tables,
and after script execution this variable is automatically destroyed, so I
can't see any security problem using this method, isn't it?
Thanks all of you. This mailing list is great! ;)
Dennis Brakhane-2 wrote:
>
> On Tue, Feb 10, 2009 at 7:04 PM, Inigo Barandiaran
> <ibarandiaran@vicomtech.org> wrote:
>> I've read that if I define an environment variable like SET
>> PGPPASSWORD=MyPosgresUserPassword, both calls dont ask for password. I've
>> tested this variable in different platforms and does not work.
>> Do you know how so solve it?
>
> As you are dealing with PostgreSQL, and not Pretty Good Privacy, I'd
> suggest removing the additional "P": PGPASSWORD, not PGPPASSWORD
>
> But .pgpass is the Right Way to do it, IMHO
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
>
--
View this message in context:
http://www.nabble.com/createdb.exe-and-psql.exe-without-Promting-Password-tp21939250p21965659.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.