From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Eugene Lisitsky <lisitsky(at)gmail(dot)com> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: PgAdmin forgets stored password on connection problem |
Date: | 2009-11-11 17:02:01 |
Message-ID: | 937d27e10911110902u1996b520v4eff2df72a6c9970@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Wed, Nov 11, 2009 at 3:33 PM, Eugene Lisitsky <lisitsky(at)gmail(dot)com> wrote:
> Is it possible to check error and fail reason: network, connection refused,
> password incorrect, no access to such DB?
Not reliably, because we only get CONNECTION_GOOD, CONNECTION_BAD as
connection status flags from libpq, and in the event of a connection
error, get a possibly-localised error message. There are no
standardised codes for connection errors (unlike query results, for
which you can get SQL status codes etc).
> Or at least as a workaround fill the form with old password?
We don't know it, unless you just typed it in. Libpq reads it from
.pgpass and pgAdmin never touches it.
>> There's definitely room for improvement here though - patches are
>> welcome if anyone wants to spend some time on it.
>
> Unfortunately I'm not a C developer. But I can try :)
:-)
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Eugene Lisitsky | 2009-11-11 17:35:29 | Re: PgAdmin forgets stored password on connection problem |
Previous Message | Dave Page | 2009-11-11 15:39:36 | Re: pgAdmin ver 1.10 freezing all too frequently |