Date: Tue, 24 Feb 2026 10:17:40 -0600
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>,
	Jelte Fennema-Nio <postgres@jeltef.nl>,
	pgsql-hackers@lists.postgresql.org,
	Andrew Dunstan <andrew@dunslane.net>
Subject: Re: pgsql: libpq: Grease the protocol by default
Message-ID: <aZ3PJG-tLJomZfck@nathan>
References: <E1vub8B-000rlS-05@gemulon.postgresql.org>
 <CAOYmi+=4QhCjssfNEoZVK8LPtWxnfkwT5p-PAeoxtG9gpNjqOQ@mail.gmail.com>
 <3626145.1771885089@sss.pgh.pa.us>
 <CAOYmi+k8ENYkErqSEYEqW39YWPfe_ii7g5Acm1c9asNuRMriNg@mail.gmail.com>
 <3635497.1771889682@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3635497.1771889682@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/aZ3PJG-tLJomZfck%40nathan>
Precedence: bulk

On Mon, Feb 23, 2026 at 06:34:42PM -0500, Tom Lane wrote:
> Jacob Champion <jacob.champion@enterprisedb.com> writes:
>> On Mon, Feb 23, 2026 at 2:18 PM Tom Lane <tgl@sss.pgh.pa.us> 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 discussed this a bit on the hacking Discord last year, but IMHO we're
reaching a good point to bump up pg_upgrade's oldest supported major
version.  I'll probably push to bump it to v10 for the v20 release so that
we can remove many of the version-specific hacks we've built up over the
years.  Not to mention that the cross-version tests (the "export
oldinstall" ones described in pg_upgrade's TESTING file, not the buildfarm
ones) don't seem to work past v10 or so because they use various options
that didn't exist or have since been renamed.

Granted, this probably doesn't help the present issue...

-- 
nathan