Re: Connection bug (was: Re: pgAdmin beta fixes)
От | Dave Page |
---|---|
Тема | Re: Connection bug (was: Re: pgAdmin beta fixes) |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E40176D81E@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответы |
Re: Connection bug
|
Список | pgadmin-support |
> -----Original Message----- > From: Erwin Brandstetter [mailto:brandstetter@falter.at] > Sent: 23 October 2006 21:08 > To: pgadmin-support@postgresql.org > Cc: Dave Page > Subject: Connection bug (was: Re: pgAdmin beta fixes) > > Steps to reproduce the crash: > Settings: ->screenshot "settings.png" > Check "Store password". Log in, providing password. (Remember, we > wouldn't need one, as we log in as system user postgres, who is on > "ident sameuser"). Disconnect. 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... :-) > Connect again. Password is being remembered, login is auto. > Disconnect > again. > Uncheck "Store password". Connect again. Do not supply password. > > An error has occurred: > fe_sendauth: no password supplied > > This message comes 3 times. (Maybe because there are 3 > databases visible?) > Focus is on the first database. (->screenshot > "before_crash.png") When I > hit <F5> now, pgAdmin crashes. > > Note: If you just try to connect without password without > these steps, > pgAdmin does not crash, you are not connected at all. And the error > message was slightly different (!!): > > An error has occurred: > Error connecting to the server: fe_sendauth: no password supplied 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. Regards, Dave.
В списке pgadmin-support по дате отправления: