11–20 of 182 posts
When I started using Django 10 years ago during the Django/Rails era, Postgres was by far the most recommended DB to use. Not sure if that was also true in Rails community.
Since the second someone found a reasonable enterprise alternative to the proctology practice that is Oracle.
Oracle fucks you in pricing, PostgreSQL in the effort required to pull off a minor version upgrade.
Asking because it's not supposed to be troublesome. In theory (!), minor version upgrades don't require any change to the on-disk data, so you should be able to just upgrade your PG binaries then restart the database.
I barely know anything about Postgres beyond installation for our use case, backup and recover. I used to know loads about obscure MySQL optimization techniques, fixing broken tables, fiddling with scary parameters and recovering from hair raising situations.
I like my current state of ignorance.
When I started using Django 10 years ago during the Django/Rails era, Postgres was by far the most recommended DB to use. Not sure if that was also true in Rails community.
When I started using Django 10 years ago during the Django/Rails era, Postgres was by far the most recommended DB to use. Not sure if that was also true in Rails community.
Way more Rails apps used MySQL or other databases, it was largely Heroku winning Rails that led to the strong adoption amongst that community.
Earlier quoted context omitted.
Oracle fucks you in pricing, PostgreSQL in the effort required to pull off a minor version upgrade.
What's the situation where minor version upgrades are giving you trouble? Asking because it's not supposed to be troublesome. In theory (!), minor version upgrades don't require any change to the on-disk data, so you should be able to just upgrade your PG binaries then restart the database.
In any case it's way more straightforward with mysql.
Earlier quoted context omitted.
What's the situation where minor version upgrades are giving you trouble? Asking because it's not supposed to be troublesome. In theory (!), minor version upgrades don't require any change to the on-disk data, so you should be able to just upgrade your PG binaries then restart the database.
Ah, looks like psql seems to have switched to actually using minor and major versions properly during the last two years - I remember the dance from the 9.x versions and postgres-upgrade [1]. In any case it's way more straightforward with mysql. [1] https://hub.docker.com/r/tianon/postgres-upgrade
https://hub.docker.com/r/pgautoupgrade/pgautoupgrade
---
That being said, those pgautoupgrade images are alpine Linux based.
People coming from non-alpine Linux images of PostgreSQL will probably need that older not-automatic approach you linked to.
When I started using Django 10 years ago during the Django/Rails era, Postgres was by far the most recommended DB to use. Not sure if that was also true in Rails community.