PostgreSQL 14 gets its final release on November 12. After that, no more fixes. Most teams I talk to have the upgrade on a list somewhere, and most of them are worried about the data: pg_upgrade, extensions, downtime.
The thing I'd worry about is smaller and later. It's a login failure that doesn't happen on upgrade day.
What changed in 14
PostgreSQL 14 changed the default of password_encryption from md5 to scram-sha-256 . Every new password is stored as a SCRAM verifier unless you change that setting.
Here's the part that makes it sneaky. pg_upgrade keeps the MD5 hashes you already have. So you upgrade a 12 or 13 server to 14 (or straight to 18), your apps reconnect, everything is green, and you close the ticket.
Then, weeks later, someone rotates the app's database password. The new one is stored as SCRAM.…