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.96) (envelope-from ) id 1vufS4-000caE-33 for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Feb 2026 23:34:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vufS3-00FsyM-1G for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Feb 2026 23:34:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vufS3-00FsyD-0L for pgsql-hackers@lists.postgresql.org; Mon, 23 Feb 2026 23:34:55 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vufRz-00000000wau-41Kn for pgsql-hackers@lists.postgresql.org; Mon, 23 Feb 2026 23:34:54 +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 61NNYgru3635498; Mon, 23 Feb 2026 18:34:42 -0500 From: Tom Lane To: Jacob Champion cc: Jelte Fennema-Nio , pgsql-hackers@lists.postgresql.org, Andrew Dunstan Subject: Re: pgsql: libpq: Grease the protocol by default In-reply-to: References: <3626145.1771885089@sss.pgh.pa.us> Comments: In-reply-to Jacob Champion message dated "Mon, 23 Feb 2026 14:51:46 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <3635496.1771889682.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 23 Feb 2026 18:34:42 -0500 Message-ID: <3635497.1771889682@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jacob Champion writes: > On Mon, Feb 23, 2026 at 2:18 PM Tom Lane wrote: >> Either that or we decide that it's time to throw 9.2 support >> overboard (looks like 9.3 and up are fine). > Well, while I was hacking on a patch I realized that 9.3 (all the way > up to 10) is only okay if you're running a sufficiently patched > version. PG11 is the first to support negotiation for the whole > release line. Hmm ... and of course the whole point of this exercise is to be sure we can pg_upgrade from those out-of-support versions. > I think Jelte said it well back on the -committers thread: >> Why only force max_protocol_version=3.0 for beta? It sounds like >> this would also be an issue once we eventually bump the default >> version. > So a fix belongs in pg_upgrade, IMO, instead of the test. I have a > draft passing locally that I should be able to share soon. Fair enough. regards, tom lane