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.org
    link
    fedilink
    English
    arrow-up
    39
    ·
    4 months ago

    0.19.4 requires upgrading Postgres (and exporting/importing the database to the new version).

    I just don’t have time for that right now since my Postgres DB is on a dedicated machine and is shared with a few other active services.

      • Admiral Patrick@dubvee.org
        link
        fedilink
        English
        arrow-up
        29
        ·
        4 months ago

        Lol, yeah.

        I think they plan to do semvar, but if I recall (and I may be wrong), since it’s pre 1.0.0, they’re “allowed” to make breaking changes since it’s still in alpha.

      • Kaboom@reddthat.com
        link
        fedilink
        English
        arrow-up
        17
        arrow-down
        4
        ·
        4 months ago

        The lemmy devs are not exactly industry developers.

        Hell, they don’t even respect gpdr, and one day the EU is going to wreck an instance and maybe an admin too if they didn’t separate liability properly.

    • Nothing4You@programming.dev
      link
      fedilink
      English
      arrow-up
      4
      ·
      4 months ago

      this isn’t true. it was incorrectly stated in the upgrade guide but has been removed a while ago. it was supposed to be a recommendation due to some issues with postgres 15. there is no postgres upgrade required between 0.19 releases.

    • woelkchen@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      7
      ·
      4 months ago

      is shared with a few other active services.

      Why would you do that, given that Lemmy is 0.x software?

      • Admiral Patrick@dubvee.org
        link
        fedilink
        English
        arrow-up
        30
        ·
        edit-2
        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.social
          link
          fedilink
          English
          arrow-up
          12
          ·
          edit-2
          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.org
            link
            fedilink
            English
            arrow-up
            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)