From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Erwin Brandstetter" <brandstetter(at)falter(dot)at>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Connection bug |
Date: | 2006-10-24 08:47:12 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40176D834@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Erwin Brandstetter [mailto:brandstetter(at)falter(dot)at]
> Sent: 23 October 2006 23:36
> To: pgadmin-support(at)postgresql(dot)org
> Cc: Dave Page
> Subject: Re: Connection bug
>
> >> An error has occurred:
> >> Error connecting to the server: fe_sendauth: no password supplied
...
>
> Sorry, crash is still reproducible. On a second thought: what
> actually
> crashes pgAdmin is the refresh.
> My special way of connecting only creates a situation, where
> refresh can do its evil deed.
> The other involved issue is, that pgAdmin requires a password, even
> where it is not required. I can live with that (especially as I
> understand what's going on an how to avoid it).
That's the thing - that message comes direct from PostgreSQL, not
pgAdmin. I was able to reproduce it by connecting with auth set to
trust, then changing to md5 and attempting to open a new database. I was
at least able to stop the refresh crash that way.
> Less prepared users might be less happy.
Yeah, though in fairness you're the first in four or five years :-)
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Harald Armin Massa | 2006-10-24 08:54:24 | anything more to install a new language? |
Previous Message | Dave Page | 2006-10-24 07:17:19 | Re: pgAdmin preBeta4 - results |