3 ms·

I pin Postgres to vMajor. But I was bitten in the rear by Wallabag the other day. Didn't work anymore. Ended up having to do a doctrine upgrade. Then it all wo

I pin Postgres to vMajor. But I was bitten in the rear by Wallabag the other day. Didn't work anymore. Ended up having to do a doctrine upgrade. Then it all worked. Same concept I guess. No automatic upgrade does allow you to pause and evaluate what you're doing, and take backups. Now I say it allows you. Whether you (or I) do so... after all, that is what automatic backups are for... Now when did I last validate those?

justinclift 3y ago
Reading through the responses, it seems like a good idea to have pgautoupgrade containers pinned to vMajor too. So (for example): pgautoupgrade/pgautoupgrade:15-alpine3.8 That one would upgrade the database to PostgreSQL 15, and not further. Simultaneously, there would be other other versions available too. For example: pgautoupgrade/pgautoupgrade:16-alpine3.8 This one would upgrade the database to PostgreSQL 16, and not further. That should be pretty straight forward to do. :)
- justinclift 3y ago
  I've just pushed an initial build with a tag for PostgreSQL 15: pgautoupgrade/pgautoupgrade:15-alpine3.8-v1 The "-v1" text fragment on the end is a version number because I'm still improving the scripting for the upgrade part. So that'll likely increment over time (-v2, -v3, -v4, etc) until it stabilises.