6 ms·
> The on-disk binary format is incompatible across major versions This is my major bugbear. If Postgres were able to upgrade its datastore on the fly (optional
by Doctor_Fegg 7y ago
> The on-disk binary format is incompatible across major versions
This is my major bugbear. If Postgres were able to upgrade its datastore on the fly (optionally, of course) that would make a massive difference. Instead I’ve had heart-in-mouth moments when Homebrew has decided that it wants to upgrade Postgres. (Yes, I do now use brew pin, until I transition off Homebrew for good.)
#2 for me is inefficient enum storage. Each value takes up 4 bytes. A single-byte enum would vastly reduce my database size.
- yardstick 7y agoRe upgrades, have you tried pg_upgrade for upgrades in place? Re enums, we had a similar thing and simply went with a smallint column instead of enum.
- yjftsjthsd-h 7y ago> Re upgrades, have you tried pg_upgrade for upgrades in place? This only works when you have both versions available at the same time, which seems likely to break when a package manager jumps major versions, and also doesn't work when running postgres in Docker (https://github.com/docker-library/postgres/issues/37 https://github.com/docker-library/postgres/issues/37).
- nasalgoat 7y agoI've found that it's incompatible with the PostGIS extension due to version differences. I'm still on 9.5 because I can't afford the downtime to properly migrate.
- sho 7y agoHomebrew added an extremely useful `brew postgresql-upgrade-database` option which will handle that. You do have to remember to run it separately. By the way, I used to have your encyclopaedia of all world knowledge
- int_19h 7y agoThis sounds like an issue with Homebrew, to some extent. On Debian, every major Postgres version gets its own package.