From: Tom Lane <tgl@sss.pgh.pa.us>
To: rekgrpth@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17032: wrong password cause double connect and double error
Date: Tue, 25 May 2021 10:12:47 -0400
Message-ID: <1209061.1621951967@sss.pgh.pa.us> (raw)
In-Reply-To: <17032-7ad69968e744de35@postgresql.org>
References: <17032-7ad69968e744de35@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, rekgrpth@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17032: wrong password cause double connect and double error
In-Reply-To: <1209061.1621951967@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox