Egregoros

@kumicota @theorytoe @tyler https://stackoverflow.com/questions/77941756/how-do-i-add-pg-repack-to-a-postgres-container

Side note: The way it is done in the answer will create 2 intermediate images that will be part of the image, but are completely useless (the apt update/install and apt remove). To do it properly, you do it the way Pleroma's Dockerfile is structured. (Build in a separate `FROM XYZ as build` and then copy only what is needed to the Postgres image. [The last FROM declaration in a Dockerfile is the base for resulting image.])

@phnt @theorytoe @tyler when I first started hosting FETI instances, my knowledge of Linux was if Ubuntu breaks, you got to reinstall Ubuntu and start over.

When people start entrusting me with their data, I felt obligated to keep it safe and learn how to keep it safe.

When migrating from NB to baest, I also took that as an opportunity to switch from Arch to Ubuntu because a rolling release distro is not the best for something like that.

Later I put the database on a ZFS, so doing backups of the database before an upgrade was as simple as taking a snapshot. Also, I could ensure the integrity of the database.

I also took dumps of the database every 12 hours.

It was a plan of mine to implement point-in-time recovery, but I never got around to it.

That being said, I always made sure to ensure that the database dumps of the database and all uploaded attachments were safe and stored on more than just the server.

I think a lot of people underestimated just how much effort I put into keeping the data of the attachments and database safe

Database and attachments were always stored in at least three physical locations and at least two separate continents.

@phnt @theorytoe @tyler @Idoru
>The wiki page does explicitly say that it is recommended to add postgres packages to the ignore list so that they don't update without the admin doing it explicitly manually.

so, here's the thing. Arch's pacman does not guarantee (or at least, this used to be the case last I used it) dynamic library dependencies. It is entirely possible that some library that PostgreSQL depends on gets yanked out from under it during an upgrade. And Postgres depends on quite a bunch of stuff.

Though, this is still much better than database corruption. But any how, you probably don't want Arch on your servers.