It seems most instances still use version 0.19.3 and the only one using the up-to-date version is lemmy.ml. They used to update relatively fast. What’s changed?

  • Admiral Patrick@dubvee.orgEnglish
    35·
    4 months ago

    Because I’m not made out of server resources lol. I’ve already got a beefy server that’s dedicated to Postgres and is well tuned, and everything else already hooks into it. I’ve also had better performance (and less overhead) with one, big well-tuned database versus lots of stack-local databases.

    If Lemmy goes tango uniform, then any damage would be limited to its schema. The worst it could really do would be resource starve it, but Zabbix would alert me of that quickly.

    • walden@sub.wetshaving.socialEnglish
      14·
      4 months ago

      My understanding is that postgres doesn’t need to be upgraded. It’ll still work with version 15 or whatever you have. Postgres 15 has some sort of memory leak that they’re trying to get away from, so they made 16 the new default.

      Same with the “requirement” to upgrade pict-rs to the latest version. You can keep the old version if you don’t care about the new image proxy feature.

      Really it’s a not a problem of needing to upgrade this stuff, but a problem with the documentation which isn’t clear. That’s a big weak spot for the Lemmy project in my opinion. I only learned the above information from lurking a bit in the Matrix chat.

      • Admiral Patrick@dubvee.orgEnglish
        4·
        4 months ago

        Good to know. Last time I recall a DB upgrade being mentioned, it was when pg15 became the new minimum so I assumed this was the same case. That one was required since they used some new feature in pg15 (don’t recall the specifics, but my test instance that was on pg14 failed the DB migrations for that lemmy release, and that was why)