3 ms·
As a developer I fully support the notion of splitting the tools out from the server engine, like things are today. But, realistically, pg_upgrade's functional
by JohnBooty 5y ago
As a developer I fully support the notion of splitting the tools out from the server engine, like things are today.
But, realistically, pg_upgrade's functionality would need to be integrated into the server itself if we're ever going to have zero-downtime upgrades, right?
I don't know how other RDBMSs handle this, if at all
- dragonwriter 5y agoYeah, the comment I was responding to addressed two different kinds of migration—schema migration and version upgrades—and my comment really applies more to schema migration than version upgrades; more support for smoothing the latter in the engine makes sense.
- JohnBooty 5y agoAgreed: Postgres' transactional schema migration is freaking sublime. I used and abused it pretty hard at my previous gig and now it's hard to imagine ever living without it. At my gig before THAT, we had MySQL and schema migrations were so very very painful.