David Fisher wrote:

>Changed the password in pgpass.conf, opened pgAdmin, went past the error
>msg, logged in with the correct password, closed pgAdmin; the correct
>password had been written to pgpass.conf.
>
>
If pgAdmin doesn't ask for the password, it won't write it to the file,
so your manual change was it. But what's the difference? Server locale,
workstation locale, database encoding?

Regards,
Andreas


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Collin Peters wrote:
> On 12/7/05, Andreas Pflug <pgadmin@pse-consulting.de> wrote:
>
>>See www.pgadmin.org
>
>
> 1.5 snapshot did not work
>
> I un-installed 1.4 (and my old 1.2 which I thought may cause some
> problems) and ran 1.5. Same problem.... I noticed it still remembered
> my server info so I found a registry key (HKCU\Software\pgAdmin III)
> deleted it and then pgadmin seemed to start up fresh (tips started
> showing up again, etc..) I then added a new server, and it was
> exactly like the process before. i.e. same error, etc...
>
>
>>>By db/user/passwd details do you mean the contents of pgpass.conf? If
>>>so it is
>>>
>>>127.0.0.1:5432:*:dbuser:dbpassword
>
>
> Well... not sure what else to say Must be something in the OS...
> some DLL or something. Like I said... the same setup works ok on
> other computers.

The new snapshot will log the password filename if debugging log is
enabled; this should be consistent with what SET APPDATA returns on a
command line. If not, let me know.

In addition, you could check for other libpq.dll versions sneaking
around on your computer; report the version you're actually using.

All I can advise further is to check with psql and manually editing
pgpass.conf, and post the difference.

Regards,
Andreas

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

An update to this thread for this issue for any future people having
the same problem

Found a fix for this. It seems that if you have the address set to
'127.0.0.1' it does not correctly use the stored password but if you
use 'localhost' it does. Very strange indeed.

On 12/9/05, Andreas Pflug <pgadmin@pse-consulting.de> wrote:
> Collin Peters wrote:
> > On 12/7/05, Andreas Pflug <pgadmin@pse-consulting.de> wrote:
> >
> >>See www.pgadmin.org
> >
> >
> > 1.5 snapshot did not work
> >
> > I un-installed 1.4 (and my old 1.2 which I thought may cause some
> > problems) and ran 1.5. Same problem.... I noticed it still remembered
> > my server info so I found a registry key (HKCU\Software\pgAdmin III)
> > deleted it and then pgadmin seemed to start up fresh (tips started
> > showing up again, etc..) I then added a new server, and it was
> > exactly like the process before. i.e. same error, etc...
> >
> >
> >>>By db/user/passwd details do you mean the contents of pgpass.conf? If
> >>>so it is
> >>>
> >>>127.0.0.1:5432:*:dbuser:dbpassword
> >
> >
> > Well... not sure what else to say Must be something in the OS...
> > some DLL or something. Like I said... the same setup works ok on
> > other computers.
>
> The new snapshot will log the password filename if debugging log is
> enabled; this should be consistent with what SET APPDATA returns on a
> command line. If not, let me know.
>
> In addition, you could check for other libpq.dll versions sneaking
> around on your computer; report the version you're actually using.
>
> All I can advise further is to check with psql and manually editing
> pgpass.conf, and post the difference.
>
> Regards,
> Andreas
>

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

On 29/3/06 19:34, "Collin Peters" <cadiolis@gmail.com> wrote:

> An update to this thread for this issue for any future people having
> the same problem
>
> Found a fix for this. It seems that if you have the address set to
> '127.0.0.1' it does not correctly use the stored password but if you
> use 'localhost' it does. Very strange indeed.

That's really bizzare. I'll look into it when I get a minute - thanks for
reporting back.

Regards, Dave.


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly