I finally got around upgrading my postgres (mastodon database), and also I restored a backup directly instead of converting the database like in previous upgrades, which confirmed that restoring a full backup works, and that also freed like 10GB of disk space. I will probably have a few hours of out of order posts while my instance catches up.
Another day I will update mastodon itself or I will switch to glitch or something.
May 8, 2026, 8:05 PM@starsider As in pg_dump backup, and running that on the new database?
I'm using the newest minor releases of some older versions, I'm wary of the update where the Docker container image changes paths.
@lukyan yeah, just a fresh postgres environment, empty database (with the user configured etc), and then:
zstd -dc /root/mastodon_production_backup_20260508_110858.sql.zst | psql -U mastodon -d mastodon_production
Dump was made with postgres 16, loaded in postgres 18.
May 8, 2026, 8:10 PM@starsider Same, these generally work.