@phnt @i I can't find the squirrel now. I've had the window open, I bet he found his way out.

@phnt @i either way altering the database in-situ at this point seems to just be inviting disaster

@phnt @i only problem is I CAN DO THAT IF I CAN'T INSTALL THE RUM EXTENSION IN THE FIRST PLACE (probably, I'd think that's how these things uually work)

@i @prettygood not really sure of the implications of that but I'll assume it's camaraderie and not "holy shit you dumbass"

@i also I really ought to be dealing with that squirrel

@i I tried just commenting it out, but that made pleroma not even start. I'll try that next time I get the database working at all (currently trying to isntall the AUR pg17)

@prettygood God doesn't want me to have a pleroma instance. I get it.

@prettygood trying to get it out of my house

@prettygood I am so drunk I am probably scaring this thing way more than is necessary

he's such a fucking asshole

and ajax picks this as a wonderufl time to bring a living, screaming, angry SQUIRREL into my house

@icst (and yeah I get it I should have proactively done the upgrade myself when I noticed the version mismatch)

@icst sheesh I am in no state to do that right now. but I will make notes and come back. this is such a headache. it seems like the install script might catch this eventuality but lol. I guess it's just a culture thing. I wasn't fully inculcated into arch

@Lyle dark meat chicken is the best meat

also I just drank maybe half a bottle of scotch so maybe this isn't the best time to be doing complex server admin junk (even if it is just a dumb hobby instance lol)

OK so here's my situation:

Arch pulled a pacman and upgraded me from postgresql 17 to postgresql 18 without prompting.

I dumbly ran this upgrade. OK fine, whatever they provide a shim in the form of posgresql-old-ugrade to get you a functional psotgres 17 environment until you can get your data exported/imported/whatever

I dumbly earlier enabled rum extensions, which apparently unlike posgresql-old-ugrade, there is no shim for. now whenever pleroma tries to access my database it complains that the rum extension can't be loaded and all queries fail. but I can see my all my old data in a data admin app on desktop.

when I try to disable rum exensions on thep leroma side (maybe it's just as simple as disabling it on the client side to make this work?) pleroma fails to start entirely. grrr probably some app-level thing idk.

am I truly hosed?

agh maybe I need to make a db dump. Or just eat the loss and start again.

I know "technically" it's my fault but still

and in the warning that pacman worked differently from other package managers, this was like the third bullet point down. it seems like this would be a much more common situation to run into, seems like it shoulda been higher but fucking hell bureaucracy! I didn't even have but a vague memory of it fucking hell

this shit doesn't seem real until it actually comes to bite you

arch forcing a major version upgrade without leaving a downgrade path to the old version and all of its extensions rofl

I hosed my fucking instance again