Updated images for MariaDB/Gitea and Postgres to latest stable or LTS #31

2023-05-08T20:04:22Z

javielico commented

2023-05-08 20:04:22 +00:00

No description provided.

3wordchant commented

2023-05-08 20:37:09 +00:00

Amazing praxis @javielico 🤘

Gitea and MySQL should be smooth, 👍 on these.

I'm a bit nervous about Postgres, because major version upgrades have been incredibly cursed when I've done them before.

They usually involve pg_dumpall / pg_restore either side of the upgrade because (from what I understand, anyway) the server app doesn't know how to upgrade data storage formats, won't launch if it detects an old data format, a pg_upgrade command exists but has some exciting requirements which are very hard to meet:

pg_upgrade functionality is perfectly clear: you need to have both postgres [old] and [new] versions installed at the same time to upgrade the data structures on disk. But what is not clear is the best way of going about the upgrade when using containers, since every container only has a single version of postgres available/installed.
— "Upgrading between major versions?"

I'm self-interestedly fine with an optimistic merge of this full PR anyway, because I'm not running any Postgres-based Gitea instances, but it would be awesome if we could include a recipe release note warning about this fiasco, and even more awesome if we could find a way to automate the upgrade somehow.

Amazing praxis @javielico 🤘 Gitea and MySQL should be smooth, 👍 on these. I'm a bit nervous about Postgres, because major version upgrades have been *incredibly* cursed when I've done them before. They usually involve `pg_dumpall` / `pg_restore` either side of the upgrade because (from what I understand, anyway) the server app doesn't know how to upgrade data storage formats, won't launch if it detects an old data format, a `pg_upgrade` command exists but has some exciting requirements which are very hard to meet: > pg_upgrade functionality is perfectly clear: you need to have both postgres [old] and [new] versions installed at the same time to upgrade the data structures on disk. But what is not clear is the best way of going about the upgrade when using containers, since every container only has a single version of postgres available/installed. > — ["Upgrading between major versions?"](https://github.com/docker-library/postgres/issues/37) I'm self-interestedly fine with an [optimistic merge](http://hintjens.com/blog:106) of this full PR anyway, because I'm not running any Postgres-based Gitea instances, but it would be awesome if we could include [a recipe release note](https://docs.coopcloud.tech/maintainers/handbook/#how-do-i-write-version-release-notes) warning about this fiasco, and even more awesome if we could find a way to automate the upgrade somehow.

javielico commented

2023-05-08 22:44:06 +00:00

Let me review on the recipe release note and see what we can do about the migration. We could perhaps bump Pgsql to a version that still updated but it's not a major upgrade? The one we had in the recipe before had reached EOL.

Thank you for reviewing the PR @3wordchant 🚀

Let me review on the recipe release note and see what we can do about the migration. We could perhaps bump Pgsql to a version that still updated but it's not a major upgrade? The one we had in the recipe before had reached EOL. Thank you for reviewing the PR @3wordchant 🚀

javielico commented

2023-05-09 19:31:49 +00:00