-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
I didn't find any information about where to file bugs on your homepage
so I will post it here:

In the "New Server" dialog, the button "OK" remains disabled until
typing into the username field. In this case "need password" is not checked.

Supplying an username and choosing OK produces "Error connecting to the
server: fe_sendauth: no password supplied", but the Postgres cluster is
not configured to require a password from the user.

Downstream Bug Report:
https://launchpad.net/distros/ubuntu...in3/+bug/60606

Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMle94L7OnT0GlBoRAtm3AJ0UyvDdxiuFtPqkAvB/P2H+Y6su2QCdF7aJ
tlQRobNz7rAieKszKfAqOjo=
=Ljbf
-----END PGP SIGNATURE-----

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

> -----Original Message-----
> From: pgadmin-hackers-owner@postgresql.org
> [mailtogadmin-hackers-owner@postgresql.org] On Behalf Of
> Martin Jürgens
> Sent: 15 October 2006 16:46
> To: pgadmin-hackers@postgresql.org
> Subject: [pgadmin-hackers] Bug: "New Server" demands password
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
> I didn't find any information about where to file bugs on
> your homepage
> so I will post it here:
>
> In the "New Server" dialog, the button "OK" remains disabled until
> typing into the username field. In this case "need password"
> is not checked.

A username is always required.

> Supplying an username and choosing OK produces "Error
> connecting to the
> server: fe_sendauth: no password supplied", but the Postgres
> cluster is
> not configured to require a password from the user.

This message comes from PostgreSQL, not pgAdmin - perhaps the users pg_hba.conf file has a password entry for the database above the trust entry? I've tested with a trusted connection with 1.6b3 and it connects with no problems without a password.

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks for your reply,

Martin


Dave Page wrote:
>
>
>> -----Original Message-----
>> From: pgadmin-hackers-owner@postgresql.org
>> [mailtogadmin-hackers-owner@postgresql.org] On Behalf Of
>> Martin Jürgens
>> Sent: 15 October 2006 16:46
>> To: pgadmin-hackers@postgresql.org
>> Subject: [pgadmin-hackers] Bug: "New Server" demands password
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>> I didn't find any information about where to file bugs on
>> your homepage
>> so I will post it here:
>>
>> In the "New Server" dialog, the button "OK" remains disabled until
>> typing into the username field. In this case "need password"
>> is not checked.
>
> A username is always required.
>
>> Supplying an username and choosing OK produces "Error
>> connecting to the
>> server: fe_sendauth: no password supplied", but the Postgres
>> cluster is
>> not configured to require a password from the user.
>
> This message comes from PostgreSQL, not pgAdmin - perhaps the users pg_hba.conf file has a password entry for the database above the trust entry? I've tested with a trusted connection with 1.6b3 and it connects with no problems without a password.
>
> 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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFM3Ns4L7OnT0GlBoRAsTsAJ9aemqv/daLjH4PEXzRLLKi1H3O7wCcDBqq
pZp0Y1+QEb+CktyRBBKxUhw=
=+fPI
-----END PGP SIGNATURE-----

---------------------------(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