On Tue, 26 Sep 2006, Tom Lane wrote:

Jeff Frost <[EMAIL PROTECTED]> writes:
Do you remember if the problem was on the 8.0.8 server side that caused the
lack of prompting?


No, I'm pretty sure it was a client-side issue (and I thought we'd fixed
it by 8.0.8 anyway, so I'm glad to see your test agrees).

Jeanna, do you maybe have a pgpass file or something else that would
short-circuit the password prompt?  It could be that your problem boils
down to supplying the wrong password behind-the-scenes.

Interestingly, I receive the same error when I disable SSL on the server:

C:\temp\pgsql\lib>..\bin\psql -h localhost -U postgres postgres
psql: FATAL: no pg_hba.conf entry for host "127.0.0.1", user "postgres", database "postgres", SSL off

But, when I put the trust line back with hostssl, I do not get connected as per her original indication. Of course this is with my 8.1.4 windows server and not 8.0.8. Is it possible that 8.0.8 was more liberal with the hostssl vs host interpretation if ssl was disabled?

I also tried making it so the postgres user could not read the server.crt and server.key files and this yielded the same result:

C:\temp\pgsql\lib>..\bin\psql -h localhost -U postgres postgres
psql: FATAL: no pg_hba.conf entry for host "127.0.0.1", user "postgres", database "postgres", SSL off

Can anyone think of an iteration I haven't tried? I'll go reset the postgres user password to something I know and start the 8.0.8 server by hand momentarily.

--
Jeff Frost, Owner       <[EMAIL PROTECTED]>
Frost Consulting, LLC   http://www.frostconsultingllc.com/
Phone: 650-780-7908     FAX: 650-649-1954


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Reply via email to