instead of

image: postgres:16-alpine

use

image: pgautoupgrade/pgautoupgrade:16-alpine

Then all the upgrade instructions of backup->update->import backups go away and all you need to do is restart the docker container. (still keep backups though!)

Reference: https://github.com/LemmyNet/lemmy/pull/4892/files

Since that pull request was merged, this will simplify future updates like 0.19.6 or 0.20.0

  • shnizmuffinA
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    2
    ·
    4 months ago

    We just had a global IT meltdown because an update wasn’t vetted properly and you have the audacity to suggest this for database infrastructure.

    • exu@feditown.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      4 months ago

      Since you’re using specific tags over just latest, it will only ever upgrade the major version to what you set.

      And it won’t change the tags magically, so you can test all of it in your separate dev environment before running it in prod.

    • Justin@lemmy.jlh.name
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      Yeah postgres updates should not be done in place, and especially not without a proper backup.