4 ms·
I think one really BIG factor is that built-in logical replication wasn't introduced until PostgreSQL 10 in 2017, before that you only had physical replication
by whizzter 2y ago
I think one really BIG factor is that built-in logical replication wasn't introduced until PostgreSQL 10 in 2017, before that you only had physical replication for master-slave but iirc that didn't work between versions so doing a "hot" upgrade was more or less impossible without third-party tools iirc.
So even if it's available these days, the amount of people still subjected to upgrades from older version still leaves an impression that it's really bad.
- creshal 2y agoYeah, everywhere I worked there's usually two clusters of postgres databases - whatever made it past the postgres 10 hump is on the most recent version and keeps getting migrated - whatever is still on 9.x is scheduled to remain that way until the product using it will be EOL'd
- RegnisGnaw 2y agoThere is still major issues with logical replication, mainly limited feature support.
- whizzter 2y agoWhat's lacking? Specific types or schema changes?
- RegnisGnaw 2y agoI don't care much about schema changes as I can setup logical replication just for the major version upgrade. The main issue is the lack of support for large objects, which the code bases I'm dealing with uses heavily.