| From: | postgresbugs <postgresbugs(at)grifent(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: PGPASSWORD |
| Date: | 2005-02-26 13:56:33 |
| Message-ID: | 42208011.4090100@grifent.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
>
> -O
That may be true. Again, I think the option to use or not use PGPASSWORD
or something similar should be up to the system administrator.
John Griffiths
| From | Date | Subject | |
|---|---|---|---|
| Next Message | postgresbugs | 2005-02-26 15:06:22 | Re: PGPASSWORD |
| Previous Message | Sergey Koshcheyev | 2005-02-26 13:09:39 | Re: BUG #1470: Boolean expression index not used when it could be |