Hi y’all,

I wrote up part one of an eventual two-part documentary/record-of-failure on how I killed and resurrected my dear lemmy instance. It’s in my instance’s meta community that isn’t federated so I thought I would share it here.

If you are like me and enjoy a technical but not overly boring look at the backside (snicker) of running a lemmy instance read on. It’s a bit of a long post so here’s a tl;dr front and center.

If there’s a better place to post this please let me know. Mods/admins, same: If I need to put this elsewhere just let me know and I’ll be happy to comply!

Best,

-oleo

https://lemmy.fan/post/182715

  • Overspark@feddit.nl
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 day ago

    PostgreSQL shitting itself is generally a hardware problem. I’ve had it “detect” faulty RAM modules in a few cases in the decades I’ve been using it.

      • TeamAssimilation@infosec.pub
        link
        fedilink
        English
        arrow-up
        3
        ·
        20 hours ago

        Postgres is pretty resilient, in my experience. If it can’t recover from a hardware failure, I’d bet no other DB would be stable on such hardware. It’s surprising how Linux can soldier on on an almost dead disk, as long as it managed to boot.