this post was submitted on 22 Jan 2025
48 points (98.0% liked)

Selfhosted

41281 readers
436 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

For those that run Element server and run postgresql version older than 13 will need to update their postgresql major version.

I found these instructions by 'maxkratz' on their github page which worked perfectly for me to go from 11 to 16.

Hopefully this helps someone!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 22 hours ago (1 children)

It's just weird that it doesn't do the dump-restore automatically when it detects data from an old version.

[–] [email protected] 1 points 4 hours ago (1 children)

I think there is a catch-22.

pg_dump needs to connect to a running PostgreSQL instance.

But if you upgrade the binaries and try to start up, you can’t because the old data format doesn’t work. Because you can’t start up, pg_dump can’t connect.

[–] [email protected] 1 points 2 hours ago

Yeah they would need to make it backwards compatible.