PostgreSQL 13 EOLs on 13 November 2025

[donsizemore]

Per https://www.postgresql.org/support/versioning/ PostgreSQL 13 EOLs on 13 November 2025. Propose that for Dataverse v6.6+ the installation docs recommend Postgres 16 or possibly 17 which is still a little new as of this writing. The current test suite succeeds in any version I've tried.

[pdurbin]

@donsizemore thanks for putting this on our radar!

As part of the following pull request...

• bump to Postgres 17, Flyway 10.19, allows earlier versions of PostgreSQL #10912

... we summarized in the 6.5 release notes the current state of PostgreSQL for Dataverse:

"### PostgreSQL and Flyway Updates

This release bumps the version of PostgreSQL and Flyway used in containers as well as the PostgreSQL JDBC driver used all installations, including classic (non-Docker) installations. PostgreSQL and its driver have been bumped to version 17. Flyway has been bumped to version 10.

PostgreSQL 13 remains the version used with automated testing, leading us to continue to recommend that version for classic installations.

As of Flyway 10, supporting older versions of PostgreSQL no longer requires a paid subscription. While we don't encourage the use of older PostgreSQL versions, this flexibility may benefit some of our long-standing installations in their upgrade paths.

As part of this update, the containerized development environment now uses Postgres 17 instead of 16. Developers must delete their data (rm -rf docker-dev-volumes) and start with an empty database (rerun the quickstart in the dev guide), as explained on the dev mailing list.

The Docker compose file used for evaluations or demos has been upgraded from Postgres 13 to 17."