Conversation

Notices

1. Embed this notice
   FWC (fwc@0.5dollah.click)'s status on Wednesday, 15-Jan-2025 05:21:36 JST FWC

   >Synapse dropped support for Postgresql v12

   Well... fuckin fantastic

   • Embed this notice
     FWC (fwc@0.5dollah.click)'s status on Wednesday, 15-Jan-2025 05:21:36 JST FWC

     in reply to

     https://www.postgresql.org/docs/current/pgupgrade.html

     prettygood likes this.
   • Embed this notice
     prettygood (prettygood@socially.drinkingatmy.computer)'s status on Wednesday, 15-Jan-2025 05:22:13 JST prettygood

     in reply to
     @fwc I say run through the upgrade process, try starting synapse connecting to a new postgres, and see what happens. Synapse should do whatever migration internally that's necessary.
   • Embed this notice
     prettygood (prettygood@socially.drinkingatmy.computer)'s status on Wednesday, 15-Jan-2025 05:28:43 JST prettygood

     in reply to
     @fwc does synapse give you any errors from an upgrade postgres? Any log info?
   • Embed this notice
     FWC (fwc@0.5dollah.click)'s status on Wednesday, 15-Jan-2025 05:28:44 JST FWC

     in reply to

     • prettygood

     @prettygood In fact, I don't think there are instructions for upgrading Postgresql from Matrix at all

   • Embed this notice
     FWC (fwc@0.5dollah.click)'s status on Wednesday, 15-Jan-2025 05:28:45 JST FWC

     in reply to

     • prettygood

     @prettygood It doesn't, though. It doesn't even link to the instructions for doing it manually.

   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Wednesday, 15-Jan-2025 05:29:29 JST Phantasm

     in reply to

     • prettygood
     @fwc @prettygood The DB version usually doesn't matter to the software connecting to it, unless it depends on some new functionality which should have been noted somewhere.
     
     The commit that removes the support has nothing of value in the message.
     ✙ dcc :pedomustdie: :phear_slackware: and prettygood like this.
   • Embed this notice
     prettygood (prettygood@socially.drinkingatmy.computer)'s status on Wednesday, 15-Jan-2025 05:30:05 JST prettygood

     in reply to

     • Phantasm
     @phnt @fwc agreed. That's why I just suggested "run pg_upgrade and try it lol" because pg_upgrade should take care of internal changes
   • Embed this notice
     sapphire (sapphire@shortstacksran.ch)'s status on Wednesday, 15-Jan-2025 05:31:39 JST sapphire

     in reply to

     • prettygood
     @fwc @prettygood that's because its completely unrelated to synapse, pg_ugprade is a postgres process that doesn't care about the database contents
     prettygood likes this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Wednesday, 15-Jan-2025 05:35:52 JST Phantasm

     in reply to

     • prettygood
     @prettygood @fwc The deprecation policy just states that they remove support for software not supported upstream.
     
     Depending on how stupid Synapse is (never tried it), I would just dump the whole DB as a backup, test the upgrade on a different system, and if all goes well, go through the upgrade process on the main system, and reindex the whole DB after the upgrade. It's always possible to rollback a version with DB backups.
     prettygood likes this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Wednesday, 15-Jan-2025 05:36:17 JST Phantasm

     in reply to

     • prettygood
     @fwc @prettygood You _can_ revert that one commit, but do you really want to set up yourself for debugging hell, when they eventually start to depend on new functionality not preset in 12?
     
     That said, I would still be running version 10, if Pleroma didn't drop support for it.
     prettygood likes this.
   • Embed this notice
     FWC (fwc@0.5dollah.click)'s status on Wednesday, 15-Jan-2025 05:36:18 JST FWC

     in reply to

     • prettygood
     • Phantasm

     @phnt @prettygood As far as I can see, there wasn't even a reason to remove the support, other than "their policies"

   • Embed this notice
     prettygood (prettygood@socially.drinkingatmy.computer)'s status on Wednesday, 15-Jan-2025 05:36:53 JST prettygood

     in reply to

     • Phantasm
     @phnt @fwc I recently upgraded my postgres server from 13 to 16 and it reduced memory usage by pleroma quite a bit. So, sometimes there's "we just made the software better" type of benefits.
   • Embed this notice
     mischievoustomato@0.5dollah.click's status on Wednesday, 15-Jan-2025 05:41:09 JST mischievoustomato

     in reply to

     @fwc try conduit if you wanna start a new one. Headache free when I ran it, and it uses some other DB software.

   • Embed this notice
     FWC (fwc@0.5dollah.click)'s status on Wednesday, 15-Jan-2025 05:41:10 JST FWC

     in reply to

     • mischievoustomato

     @mischievoustomato Think I should bother, or just start a new matrix instance?

   • Embed this notice
     prettygood (prettygood@socially.drinkingatmy.computer)'s status on Wednesday, 15-Jan-2025 05:42:23 JST prettygood

     in reply to

     • mischievoustomato
     @mischievoustomato @fwc conduit uses RocksDB or sqlite. I have hella problems with conduit and joining rooms on Synapse servers, so I'm going to ditch it when I get the time to scour around in the database to find the keys so that migrating isn't a complete disaster.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.