Re: BUG #17032: wrong password cause double connect and double error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: rekgrpth(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17032: wrong password cause double connect and double error
Date: 2021-05-25 14:12:47
Message-ID: 1209061.1621951967@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-05-25 22:58:31 BUG #17034: Creating aggregate function based on array_append now results in "function does not exist" error
Previous Message RekGRpth 2021-05-25 14:10:11 Re: BUG #17032: wrong password cause double connect and double error