Re: BUG #17032: wrong password cause double connect and double error - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17032: wrong password cause double connect and double error
Date
Msg-id 1209061.1621951967@sss.pgh.pa.us
Whole thread Raw
In response to BUG #17032: wrong password cause double connect and double error  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> 5) get double error on client side:

That's normal behavior, if you're using an SSL-capable libpq over a TCP
socket; it will try once with SSL and once without.  (This isn't quite
as insane as it perhaps sounds, because the server might have different
pg_hba rules for the two cases.)  If you don't want that, you can force
the matter using the sslmode connection option.

            regards, tom lane



pgsql-bugs by date:

Previous
From: RekGRpth
Date:
Subject: Re: BUG #17032: wrong password cause double connect and double error
Next
From: PG Bug reporting form
Date:
Subject: BUG #17034: Creating aggregate function based on array_append now results in "function does not exist" error