| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PGPASSWORD and client tools |
| Date: | 2004-08-19 01:42:37 |
| Message-ID: | 6839.1092879757@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> 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 notice it was deprecated either - it's the only way that
> phpPgAdmin can integrate with pg_dump...
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 any other
method I'd recommend on a multiuser machine.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-08-19 01:54:02 | Re: pg_dump 'die_on_errors' |
| Previous Message | Christopher Kings-Lynne | 2004-08-19 01:40:23 | Re: Tablespace and cpu costs |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-08-19 01:54:02 | Re: pg_dump 'die_on_errors' |
| Previous Message | Christopher Kings-Lynne | 2004-08-19 01:38:16 | Re: PGPASSWORD and client tools |