The first thing that happens when you point pg_upgrade at a fresh PostgreSQL 18 cluster is, quite often, nothing. It refuses. That refusal is the most useful thing in this release for anyone running a Django app, because it forces you to look at a default that changed underneath you β and there are four more like it.
PostgreSQL 18 was released on 25 September 2025 . Django 6.0 arrived that December and supports PostgreSQL 14 and higher , so nothing in the ORM forces the move. What follows is what I actually check before moving a Django project onto 18, in the order the problems show up.
The upgrade refuses before it starts
initdb in 18 now defaults to enabling data checksums , with a new --no-data-checksums flag to turn them off. pg_upgrade requires that the old and new clusters agree on checksum settings.β¦