Re: Database bar (was: Re: Beta 3 crashing reproducably)

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: Database bar (was: Re: Beta 3 crashing reproducably)
Date: 2006-10-29 20:10:46
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40176D990@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: 27 October 2006 19:13
> To: pgadmin-support(at)postgresql(dot)org
> Cc: Dave Page
> Subject: Database bar (was: Re: [pgadmin-support] Beta 3
> crashing reproducably)
>
> After further testing I could narrow down the cause.
> When I try to connect to another database on the same host (same
> IP-address), then a database of the _same name_ as the one of the
> current connection is not listed and cannot be chosen.
> Concerns connections on different port or with different login. This
> happens to be the one situation where the feature would be
> most useful
> (to me).
> Tested with plain TCP/IP connection to a remote server as
> well as with
> SSH-connection and portforwarding.
> Contrary to initial suspicions, maintainance DB seems to be unrelated.

Yep, confirmed and fixed in SVN.

Thanks, Dave.

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Raymond O'Donnell 2006-10-29 22:50:27 Parentheses
Previous Message Dave Page 2006-10-29 19:53:04 Re: Bug in Report on Statistcs