Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tLU0z-00F5DN-Gw
	for pgsql-bugs@arkaria.postgresql.org; Wed, 11 Dec 2024 21:13:01 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tLU0w-002lR5-07
	for pgsql-bugs@arkaria.postgresql.org; Wed, 11 Dec 2024 21:12:59 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tLU0v-002lQx-NS
	for pgsql-bugs@lists.postgresql.org; Wed, 11 Dec 2024 21:12:58 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tLU0n-002KRF-QR
	for pgsql-bugs@lists.postgresql.org; Wed, 11 Dec 2024 21:12:57 +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 4BBLCk0K525599;
	Wed, 11 Dec 2024 16:12:46 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Bossart <nathandbossart@gmail.com>
cc: Thomas Munro <thomas.munro@gmail.com>,
        Bertrand Drouvot <bertranddrouvot.pg@gmail.com>,
        Bruce Momjian <bruce@momjian.us>, adam@labkey.com,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18711: Attempting a connection with a database name longer
 than 63 characters now fails
In-reply-to: <Z1n9I4MBers-si82@nathan>
References: <Z0Dmw1ryKH8bEkyo@nathan> <Z0c9XVU6aTd8neRr@nathan>
 <1865227.1732723416@sss.pgh.pa.us>
 <CA+hUKGKKNAc599Vp7kFAnLE1=V=ceYujz_YQoSNrvNFGaJ6i7w@mail.gmail.com>
 <2094158.1732812306@sss.pgh.pa.us>
 <CA+hUKGKDC7tKMZ1v0JGH5D23F-=ADf-3UfcriVepqoi7Q_SKgQ@mail.gmail.com>
 <Z0mUMnVakLOizwID@ip-10-97-1-34.eu-west-3.compute.internal>
 <CA+hUKG+uJGt2tks0jyS=Gkjd0Uig-9cORVm-_igp50m7QwKrWw@mail.gmail.com>
 <Z061kNj9z0Nic5EF@ip-10-97-1-34.eu-west-3.compute.internal>
 <CA+hUKG+n6ag0QNDCRP-Yhgr-aFRKvvdKdo_O57y=z5ry8cNNVQ@mail.gmail.com>
 <Z1n9I4MBers-si82@nathan>
Comments: In-reply-to Nathan Bossart <nathandbossart@gmail.com>
	message dated "Wed, 11 Dec 2024 14:59:15 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <525597.1733951566.1@sss.pgh.pa.us>
Date: Wed, 11 Dec 2024 16:12:46 -0500
Message-ID: <525598.1733951566@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/525598.1733951566%40sss.pgh.pa.us>
Precedence: bulk

Nathan Bossart <nathandbossart@gmail.com> writes:
> If we are leaning towards a more comprehensive fix in v18, ISTM we should
> go ahead and revert commit 562bee0 (both for master and v17).  Or am I
> misinterpreting the proposed path forward here?

That seems like a reasonable thing to do now, since we have a
complaint about v17's behavior and there seems no compelling
reason why v17 has to address this ancient issue.

			regards, tom lane