Pgadmin - Re: Connection bug

Author

Re: Connection bug

Erwin Brandstetter

2006-10-25, 8:27 am

dpage@vale-housing.co.uk wrote:
> OK, I should warn you that connecting like this is completely untested
> and not something we've ever said we'll support. But I'll do what I
> can... :-)
>

You might consider this method of connecting tested now - I tested it a
lot over the last few years. :)
It works just fine, except for the reported problem. But I can connect
otherwise.
The upside of this method is that I can connect without password (or
saving passwords anywhere on the disc) and still have the security of an
RSA-key for SSH (using puTTY and pageant for this).

>
> I've made a couple of changes to fix the password related issues that
> George reported. I have a hunch that the second fix might resolve your
> problem. I'll mail across an update in a minute for testing if you
> wouldn't mind.
>

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). Less prepared users
might be less happy.

Regards
Erwin

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Dave Page

2006-10-25, 8:27 am

> -----Original Message-----
> From: Erwin Brandstetter & #91;mailto:brandstet
ter@falter.at]
> Sent: 23 October 2006 23:36
> To: pgadmin-support@postgresql.org
> Cc: Dave Page
> Subject: Re: Connection bug
>

....
[color=darkred]
>
> 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.

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Sponsored Links