Skip to content

Comment on Waiting for Postgres 16: Cumulative I/O statistics with pg_stat_ioparent

Comments

Because PostgreSQL major version upgrades are hard and for large databases, requires some level of downtime. Given that that major version releases are on an annual release cycle, staying evergreen is really really annoying.

Under some elementary scenarios (and using some Postgres offerings), you can do a full major upgrade using logical replication (even with replicas). It depends on your situation, generally I agree, any sophisticated use of Postgres (lot of views, materialized or not, fast changing schema, large objects, and so on) makes upgrades a pain and is generally somewhat of an unresolved problem in my opinion.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.