Re: [HACKERS] PGPASSWORD and client tools

2004-12-02 Thread Christopher Kings-Lynne
Please ignore- seems some old mail of mine got sent waaay late... Christopher Kings-Lynne wrote: While fixing the gui for pg_dump and pg_restore, I painfully noticed there's no option for the password. After some tests, I found that using the PGPASSWORD environment variable will do the job. I'm a

Re: [HACKERS] PGPASSWORD and client tools

2004-12-02 Thread Christopher Kings-Lynne
While fixing the gui for pg_dump and pg_restore, I painfully noticed there's no option for the password. After some tests, I found that using the PGPASSWORD environment variable will do the job. I'm a bit irritated that it's marked "deprecated" in the docs, the .pgpass solution isn't a good one

Re: [HACKERS] PGPASSWORD and client tools

2004-08-19 Thread Andrew Dunstan
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 need

Re: [HACKERS] PGPASSWORD and client tools

2004-08-19 Thread Andreas Pflug
Christopher Kings-Lynne wrote: It's deprecated because it's insecure, on platforms where other users can see the environment variables passed to pg_dump (which apparently is quite a few variants of Unix). You wouldn't pass the password on the command line either ... Painful as .pgpass may be for a

Re: [HACKERS] PGPASSWORD and client tools

2004-08-18 Thread Magnus Hagander
>>>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 satis

Re: [HACKERS] PGPASSWORD and client tools

2004-08-18 Thread Andrej Czapszys
Tom Lane wrote: It's deprecated because it's insecure, on platforms where other users can see the environment variables passed to pg_dump (which apparently is quite a few variants of Unix). You wouldn't pass the password on the command line either ... Painful as .pgpass may be for an admin tool, I

Re: [HACKERS] PGPASSWORD and client tools

2004-08-18 Thread Andrew Dunstan
Tom Lane wrote: Andrew Dunstan <[EMAIL PROTECTED]> writes: 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 PGP

Re: [HACKERS] PGPASSWORD and client tools

2004-08-18 Thread Tom Lane
Andrew Dunstan <[EMAIL PROTECTED]> writes: > 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

Re: [HACKERS] PGPASSWORD and client tools

2004-08-18 Thread Andrew Dunstan
Tom Lane wrote: Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: After some tests, I found that using the PGPASSWORD environment variable will do the job. I'm a bit irritated that it's marked "deprecated" in the docs, the .pgpass solution isn't a good one for tool managed passwords.

Re: [HACKERS] PGPASSWORD and client tools

2004-08-18 Thread Christopher Kings-Lynne
It's deprecated because it's insecure, on platforms where other users can see the environment variables passed to pg_dump (which apparently is quite a few variants of Unix). You wouldn't pass the password on the command line either ... Painful as .pgpass may be for an admin tool, I do not know of

Re: [HACKERS] PGPASSWORD and client tools

2004-08-18 Thread Tom Lane
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: >> After some tests, I found that using the PGPASSWORD environment variable >> will do the job. I'm a bit irritated that it's marked "deprecated" in >> the docs, the .pgpass solution isn't a good one for tool managed passwords. > I didn't notic

Re: [HACKERS] PGPASSWORD and client tools

2004-08-18 Thread Christopher Kings-Lynne
While fixing the gui for pg_dump and pg_restore, I painfully noticed there's no option for the password. After some tests, I found that using the PGPASSWORD environment variable will do the job. I'm a bit irritated that it's marked "deprecated" in the docs, the .pgpass solution isn't a good one

[HACKERS] PGPASSWORD and client tools

2004-08-18 Thread Andreas Pflug
While fixing the gui for pg_dump and pg_restore, I painfully noticed there's no option for the password. After some tests, I found that using the PGPASSWORD environment variable will do the job. I'm a bit irritated that it's marked "deprecated" in the docs, the .pgpass solution isn't a good one