Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1llXnh-00063p-V2
	for pgsql-bugs@arkaria.postgresql.org; Tue, 25 May 2021 14:12:53 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1llXng-0008DP-0u
	for pgsql-bugs@arkaria.postgresql.org; Tue, 25 May 2021 14:12:52 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1llXnf-0008DH-Qe
	for pgsql-bugs@lists.postgresql.org; Tue, 25 May 2021 14:12:51 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1llXnd-0005Gu-NQ
	for pgsql-bugs@lists.postgresql.org; Tue, 25 May 2021 14:12:50 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 14PEClgp1209062;
	Tue, 25 May 2021 10:12:47 -0400
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
In-reply-to: <17032-7ad69968e744de35@postgresql.org>
References: <17032-7ad69968e744de35@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 25 May 2021 11:50:30 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1209060.1621951967.1@sss.pgh.pa.us>
Date: Tue, 25 May 2021 10:12:47 -0400
Message-ID: <1209061.1621951967@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/1209061.1621951967%40sss.pgh.pa.us>
Precedence: bulk

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