Horton
Menu

Re: bump minimum supported version of psql and pg_{dump,dumpall,upgrade} to v10

Nathan Bossart <nathandbossart@gmail.com>

View thread
From: Nathan Bossart <nathandbossart@gmail.com>
To: Corey Huinker <corey.huinker@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2026-04-08T18:04:02Z
Lists: pgsql-hackers 
On Wed, Apr 08, 2026 at 01:24:29PM -0400, Corey Huinker wrote:
> It would help if we provided some small documentation on how to do that. It
> could be as simple as a docbook table mapping various postgres versions to
> the highest version a) a live database can be pg_upgraded to and b) a
> dumpfile can be pg_restored to. But it could also include a script to
> re-dump an old dumpfile to a newer dump version. I'd be happy to take a
> swing at that if nobody else is interested.

I like these ideas.  IMHO this helps us be reasonably aggressive about
removing support for ancient versions while still providing a lifeboat when
folks using those ancient versions decide to upgrade.

-- 
nathan

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove pg_dump/pg_dumpall support for dumping from pre-v10 servers.

  2. Remove pg_upgrade support for upgrading from pre-v10 servers.

  3. Remove psql support for pre-v10 servers.

  4. Run pgindent and pgperltidy for previous 3 commits.