PostgreSQL 12 Reaches End of Life: What You Need to Know
PostgreSQL users, take note! Your favorite open-source database is rapidly approaching a major milestone: the end of life (EOL) for version 12. With less than a month remaining before support drops, it’s critical to start planning your migration.
The Clock is Ticking
Introduced in 2019, PostgreSQL 12 has served developers faithfully for nearly four years. Now approaching its five-year anniversary, the PostgreSQL Global Development Group adheres to a strict EOL policy: after five years, a single minor release containing only bug fixes will be issued, followed by completion of support for that version.
Who’s Still Using PostgreSQL 12?
Despite the looming deadline, data suggests a surprisingly high number of users remain on this outdated version. Percona, a company specializing in open-source database support, reports that around 11% of deployed PostgreSQL databases are currently running on version 12. This figure, drawn from telemetry data collected through Percona’s database management product PMM, paints a striking picture of the urgency surrounding this issue.
A Legacy of Cloud and Delay
Technological advancements and shifting priorities likely contribute to the continued use of PostgreSQL 12. Alastair Turner, Technical Evangelist at Percona, highlights the popularity of cloud database services as a key factor. "The people who may then feel they have to retest their entire application, maybe just because internal processes require it, are developers," he explains. Additionally, modernization programs, often complex and prone to delays, commonly drive database upgrades.
Beware the Transition Snags
While the latest release, PostgreSQL 17, boasts exciting features like incremental backup, it’s unlikely to be the primary destination for users seeking to escape version 12. Turner advises that PostgreSQL 16 presents a more practical and seamless migration path.
However, be warned: users migrating from versions between 12 and 16 should be aware of adjustments made to standards compliance and object creation within the default schema. As Turner explains, "If you’re upgrading an application in place, you probably won’t see any problems, but [if users are] trying to create their database structures the first time they start up, they may bump into some issues.”
Don’t Wait, Plan Your Migration Today
The end-of-life date for PostgreSQL 12 is fast approaching. Take action now to ensure your applications and databases remain secure, stable, and supported. Reach out to your development team, explore migration options, and take steps towards a smooth transition to a supported version of PostgreSQL.