From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 2 forks for md5? |
Date: | 2005-09-22 03:30:24 |
Message-ID: | 24170.1127359824@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Confusion fixed (thanks, Tom). psql (via libpq) tries twice, if not
> given a password to begin with (via .pgpass or psql's -W).
> Ugly but at least not incomprehensible.
This seems reasonable behavior when prompting for a password from the
user, since that's going to take a lot of time anyway. I'm not sure
whether libpq should try to excavate a password from ~/.pgpass in
advance of being told by the server that one is needed.
An ideal solution might be to read ~/.pgpass during the bit of code that
handles a password challenge from the server, rather than in the "outer
loop". Not having looked at the libpq code recently, I have no idea how
painful that would be to do.
Comments?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2005-09-22 05:41:19 | Re: feature proposal ... |
Previous Message | Tom Lane | 2005-09-22 03:18:25 | Re: 2 forks for md5? |