Post B0PuXhvGoAPCtLSkTo by bajax@baj.ax
(DIR) More posts by bajax@baj.ax
(DIR) Post #B0PamzZBUdH0sD8w3E by Bajax@froth.zone
2025-11-19T18:33:01.285913Z
0 likes, 0 repeats
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/whateverI 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.
(DIR) Post #B0Pb5Bil2fAXmYIVZw by Bajax@froth.zone
2025-11-19T18:36:19.628936Z
0 likes, 0 repeats
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)
(DIR) Post #B0Pci7fc8V34T0xMVU by i@declin.eu
2025-11-19T18:54:31.427685Z
1 likes, 0 repeats
@Bajax dunno, add `config :pleroma, :database, rum_enabled: false` maybe?https://aur.archlinux.org/pkgbase/postgresql17 is also back now that 18 is in the repo's, you could move your data back into that too
(DIR) Post #B0PdC5sdM7SDbRKzku by Bajax@froth.zone
2025-11-19T18:59:57.956043Z
0 likes, 0 repeats
@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)
(DIR) Post #B0PdDnDViTXiIaueNE by Bajax@froth.zone
2025-11-19T19:00:18.146656Z
0 likes, 0 repeats
@i also I really ought to be dealing with that squirrel
(DIR) Post #B0PdFCv7dZ7cJ2zCvg by phnt@fluffytail.org
2025-11-19T19:00:31.451832Z
1 likes, 1 repeats
@i Might also require reverting the optional RUM migration, because it technically still exists in the DB and Postgres might not like that.@Bajax Alternatively build RUM yourself for now before it is packaged, since the latest version supports 18.
(DIR) Post #B0PdJZ1rNawO28DOuu by Bajax@froth.zone
2025-11-19T19:01:20.645515Z
0 likes, 0 repeats
@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)
(DIR) Post #B0PdLFeQOhaGVr3fSy by Bajax@froth.zone
2025-11-19T19:01:39.677596Z
0 likes, 0 repeats
@phnt @i either way altering the database in-situ at this point seems to just be inviting disaster
(DIR) Post #B0PdN87VMtlpjdYWtk by mint@ryona.agency
2025-11-19T19:01:57.915527Z
1 likes, 1 repeats
@Bajax Never used postgres on Arch, but on Debian and Alpine you just had to have both old and new versions installed, then build and run extensions (RUM and pg_repack in my case) for the newer version before running pg_upgrade, otherwise it'll refuse to do the upgrade. Did the upgrade somehow succeed?
(DIR) Post #B0PdTwWEtoIhmYNF2W by Bajax@froth.zone
2025-11-19T19:03:08.212986Z
0 likes, 0 repeats
@phnt @i I can't find the squirrel now. I've had the window open, I bet he found his way out.
(DIR) Post #B0Pdd6mA8MX8CQByiW by mint@ryona.agency
2025-11-19T19:04:51.025389Z
2 likes, 1 repeats
@Bajax https://wiki.archlinux.org/title/PostgreSQL?useskin=vector#Failing_to_start_a_PostgreSQL_server_with_the_older_version_of_the_database_while_upgrading_to_the_newer_version_with_extensionsIf you installed RUM from source, .so files should still be in place, if not grab them from package cache or something.
(DIR) Post #B0PdkibrrmkjZB0QCW by Bajax@froth.zone
2025-11-19T19:06:10.208899Z
1 likes, 0 repeats
@mint I know, that's why the postgresql-old-upgrade package was included in the main package repo... but it doesn't include the extensions (pg_rum in this case), which you need if you're gonna do a direct binary-to-binary upgrade like that-- meaning that if you use them, that upgrade path is just blocked for you. aiyiyi dios mio
(DIR) Post #B0PdtCH9SAintFMIwC by Bajax@froth.zone
2025-11-19T19:07:42.056380Z
1 likes, 0 repeats
it's such a weird confluence of oversight and "why the hell would you enable RUM? nobody else does."
(DIR) Post #B0PeFNyGePDAX96eXY by phnt@fluffytail.org
2025-11-19T19:11:46.813985Z
2 likes, 1 repeats
@mint @Bajax Also for the future upgrade, putting all the Postgres packages into IgnorePkg in pacman.conf is a good idea.
(DIR) Post #B0PeJijLPU6q4lC27s by Bajax@froth.zone
2025-11-19T19:12:34.563042Z
0 likes, 0 repeats
@phnt @mint I'll just have to check for upgrades manually (if I care/remember at all lol)
(DIR) Post #B0PeQfJiV0hbW5W9WC by phnt@fluffytail.org
2025-11-19T19:13:48.066286Z
0 likes, 1 repeats
@Bajax @mint The files for the extension should still be in the install location for the new version since pacman has no idea those exists so they stay.
(DIR) Post #B0PeTXIoklkPWqSwpU by phnt@fluffytail.org
2025-11-19T19:14:20.677043Z
1 likes, 1 repeats
@Bajax @mint It gives you a warning on every update that packages have been ignored due to that setting.
(DIR) Post #B0PeYqc0O9a8rcyPui by Bajax@froth.zone
2025-11-19T19:15:17.469482Z
0 likes, 0 repeats
@phnt @mint well, it's worth a shot if I can manage to get the old cached package installed at all (running into incomprehensible package manager issues-- it seems to thinks files exist that clearly DON'T) right now the postgresql-old-upgrade shim can't see the rum extensions wherever they are. may need to compile them from source or something?
(DIR) Post #B0PeaoD4I67nzcFDyy by Bajax@froth.zone
2025-11-19T19:15:39.986154Z
0 likes, 0 repeats
@phnt @mint (that's an option I'd been considering I mean)
(DIR) Post #B0PeeCnrJGKf8X4ZU0 by Bajax@froth.zone
2025-11-19T19:16:16.938161Z
0 likes, 0 repeats
@phnt @mint god this is all terra incognita how often does someone get this lost in the sauce and actually get their data back lol
(DIR) Post #B0PehvXXR5X8koDIcC by phnt@fluffytail.org
2025-11-19T19:16:57.063856Z
0 likes, 1 repeats
@Bajax @mint How did you even install it in the first place.
(DIR) Post #B0PelIxIplKKFEsKI4 by phnt@fluffytail.org
2025-11-19T19:17:33.220847Z
0 likes, 1 repeats
@Bajax @mint Also backup the whole /var/lib/pgsql directory now just to be safe.
(DIR) Post #B0PeoQGo5wbbncU7zE by Bajax@froth.zone
2025-11-19T19:18:07.342881Z
1 likes, 0 repeats
@phnt @mint did that at the outset lol just haivng trouble accessing it in any reliable way because it can't operate without that presumably very rare extension
(DIR) Post #B0PerhGTMjxPNMtE9I by Bajax@froth.zone
2025-11-19T19:18:43.192336Z
0 likes, 0 repeats
@phnt @mint I don't really want to just strip the indexes away because there's no guarantee any migration could get them back
(DIR) Post #B0PeuYhBgLUrfTkYrY by Bajax@froth.zone
2025-11-19T19:19:14.194012Z
0 likes, 0 repeats
@mint @phnt aught I guess I could just dump the raw data into an empty initi'd db but I'm getting really close to just saying "fuck it" territory
(DIR) Post #B0Pexl0WMabsimJnUG by i@declin.eu
2025-11-19T19:19:47.217392Z
0 likes, 0 repeats
@Bajax @phnt @mint don't have to finish it today, give it an evening
(DIR) Post #B0Pf2NYQzLfpQmNv3Q by mint@ryona.agency
2025-11-19T19:20:37.121541Z
2 likes, 1 repeats
@Bajax @phnt I mean, you don't even need to install the rum package, just unzip it and grab the files from there.
(DIR) Post #B0PfUuArIovMhvxZPE by Bajax@froth.zone
2025-11-19T19:25:47.886149Z
0 likes, 0 repeats
@mint @phnt that's right, duh
(DIR) Post #B0PgEmxQSxd1e8YVxA by Bajax@froth.zone
2025-11-19T19:34:04.891502Z
0 likes, 0 repeats
@phnt @mint like I'm having to learn a whole lot of shit about how all this shit works which I wasn't planning on today. just fucking blunder after blunder lol
(DIR) Post #B0Pgw5VbMvkfdNBhr6 by Bajax@froth.zone
2025-11-19T19:41:53.647543Z
0 likes, 0 repeats
@i @phnt @mint I'll do so, but I think I'm at a point where I don't really care about sysadmin stuff as much as I used to. That's how I got into this mess in the first place-- and while solving this issue and getting my instance back seems like a cool challenge and something that seems completely workable, I just don't really want to put the time into it. I've got so much other stuff going on
(DIR) Post #B0Ph2axtKOpuvoWUOu by i@declin.eu
2025-11-19T19:43:04.152657Z
3 likes, 0 repeats
@Bajax @phnt @mint if all else fails, give some one else creds and let em fix it
(DIR) Post #B0Pr13TvKdnEKwPUoK by Bajax@froth.zone
2025-11-19T21:34:51.704829Z
0 likes, 0 repeats
@i @phnt @mint just as I thought-- it needs pg_rum in order to roll back the migrations so I don't need rum... fucking hell do I need to do database surgery, manually delete and roll back all the rum stuff?
(DIR) Post #B0PrxfKKmXNiVXs9OC by i@declin.eu
2025-11-19T21:45:25.758488Z
1 likes, 0 repeats
@Bajax @phnt @mint take the time to do the upgrade proper, compile rum and let err rip
(DIR) Post #B0Ps6GgPmCk8gNIoIy by Bajax@froth.zone
2025-11-19T21:46:59.273880Z
0 likes, 0 repeats
@i @phnt @mint tried that. needs a whole build environment apparently-- it keeps seeking a higher level directory for make files, like this repo is just a submodule that builds against a specific postgre ver--- I need to build the entirety of psql17 from source don't I?
(DIR) Post #B0Ps6zqDsaKKjpEmLA by Bajax@froth.zone
2025-11-19T21:47:09.739768Z
0 likes, 0 repeats
@i @mint @phnt nope. not tonight. Doing that tomorrow
(DIR) Post #B0PsREJJnChnPCUin2 by Bajax@froth.zone
2025-11-19T21:50:46.776466Z
0 likes, 0 repeats
@i @mint @phnt (I' sure I'm being retarded and you're all laughing at me)
(DIR) Post #B0PsYaLuExirnHDE8G by i@declin.eu
2025-11-19T21:52:06.169075Z
1 likes, 0 repeats
@Bajax @phnt @mint nah, but the instructions did work on arch on my machine, so do take an evening of rest before trying again
(DIR) Post #B0PsbanJ3O9s27SjfE by phnt@fluffytail.org
2025-11-19T21:52:37.718771Z
0 likes, 1 repeats
@Bajax @i @mint >I need to build the entirety of psql17 from source don't I?Shouldn't need to, both the main and old-upgrade packages ship PGXS. But it might get confused on what Postgres version you mean to build against (always builds against 18).
(DIR) Post #B0PsglXSX9DMnvW71s by phnt@fluffytail.org
2025-11-19T21:53:36.341014Z
0 likes, 1 repeats
@i @Bajax @mint I've packaged it for RHEL and those instructions also work there. gcc, make and Postgres development headers are all what is needed.
(DIR) Post #B0Psi7QcdLemz2xq2C by Bajax@froth.zone
2025-11-19T21:53:46.516245Z
0 likes, 0 repeats
@phnt @i @mint I pointed rum's makefile at my local pg_config that seemingly/supposedly outputs all the header information it should need to build properly and it wouldn't.
(DIR) Post #B0PsjrUwphHy9jools by Bajax@froth.zone
2025-11-19T21:54:10.319800Z
0 likes, 0 repeats
@phnt @i @mint it... yeah got confused about the version. I don't know how to set it straight
(DIR) Post #B0PsossR8LrtseCT3o by Bajax@froth.zone
2025-11-19T21:55:04.904731Z
0 likes, 0 repeats
@i @mint @phnt I probably have yeah I have the wrong rum don't I. augh the git version tags don't indicate which pg it's meant to build against
(DIR) Post #B0Pt1XmuqysyEqedwO by Bajax@froth.zone
2025-11-19T21:57:21.726052Z
1 likes, 0 repeats
@i @phnt @mint I'm on arch btw don't remember if I said in this thread but I'm on arch
(DIR) Post #B0Pt7XfKDnqjb1xpku by phnt@fluffytail.org
2025-11-19T21:58:25.156210Z
0 likes, 1 repeats
@Bajax @i @mint Shouldn't need to. I've found a different funky thing in the Make file: https://github.com/postgrespro/rum/blob/master/Makefile#L38Which I think resets your PG_CONFIG if you else set USE_PGXS=1 so your setting doesn't take effect. Try removing USE_PGXS=1 and only set PG_CONFIG.
(DIR) Post #B0PtTzsE1dGpS8hn7Y by Bajax@froth.zone
2025-11-19T22:02:28.882763Z
0 likes, 0 repeats
@phnt @i @mint damn it's building
(DIR) Post #B0PtwvGgEBCXZCw8fY by bajax@baj.ax
2025-11-19T22:07:42.701488Z
2 likes, 0 repeats
@Bajax @phnt @mint there. fixed it. Thank you phnt that option made it build properly, then I manually copied it into place.
(DIR) Post #B0PtyCyLtA4ilWydCy by bajax@baj.ax
2025-11-19T22:07:58.569873Z
0 likes, 0 repeats
@Bajax @mint @phnt now to set aside time tomorrow to do the migration right lol
(DIR) Post #B0PuMdHViwzbJNaJGa by phnt@fluffytail.org
2025-11-19T22:12:22.811427Z
0 likes, 1 repeats
@bajax @Bajax @mint @i Shouldn't be that hard from now on. Build the extension for 18, install it, do a full DB backup just in case, stop Postgres 17, run pg_upgrade, start Postgres 18 proper, run `vacuumdb --analyze-in-stages -a` and should be everything.
(DIR) Post #B0PuXhvGoAPCtLSkTo by bajax@baj.ax
2025-11-19T22:14:23.521614Z
0 likes, 0 repeats
@phnt @i @Bajax @mint yeah it should be extremely easy now lol that's just the next step in every article and forum post I'm finding about it
(DIR) Post #B0Pv1OKOE3nKo5Mn5c by i@declin.eu
2025-11-19T22:19:41.515173Z
3 likes, 0 repeats
@bajax @phnt @Bajax @mint grats on making it
(DIR) Post #B0PwfPYbAuMg9lewro by bajax@baj.ax
2025-11-19T22:38:11.763507Z
0 likes, 0 repeats
@phnt @i @Bajax @mint how did you know to look for this btw?
(DIR) Post #B0PwwopETtnFRojy64 by phnt@fluffytail.org
2025-11-19T22:41:17.733455Z
1 likes, 1 repeats
@bajax @i @Bajax @mint I didn't. You mentioned that the build system gets confused and that it might not be version agnostic and I decided to check how that would be and found that while I was there.
(DIR) Post #B0PxCUpsZNr85IWD3I by bajax@baj.ax
2025-11-19T22:44:08.385798Z
1 likes, 0 repeats
@phnt @i @Bajax @mint well what confused things is I had more than one way to try and build it-- there's one package in the AUR which seems to handle building it against the local version and then installing it, but it had complicated header issues that looked like actual version incompatibility-- it was complaining about function signatures not matching etc. that's why I thought it might not be version agnostic. the cloned git repo of rum was what eventually worked.
(DIR) Post #B0PxFGdlnuMwvYAy3c by bajax@baj.ax
2025-11-19T22:44:40.297867Z
0 likes, 0 repeats
@phnt @Bajax @i @mint idk it worked we're clear now awesome
(DIR) Post #B0PxMEDpC6InSBMLaq by phnt@fluffytail.org
2025-11-19T22:45:55.156973Z
1 likes, 1 repeats
@bajax @i @Bajax @mint >there's one package in the AUR which seems to handle building it against the local version and then installing it, but it had complicated header issues that looked like actual version incompatibility-- it was complaining about function signatures not matching etc. That checks out since the package hasn't been update for 3 years and the version that is there doesn't support 17 and later.
(DIR) Post #B0PxVlim0xDhxJNuNs by bajax@baj.ax
2025-11-19T22:47:39.356167Z
0 likes, 0 repeats
@phnt @i @Bajax @mint oh lol probably should have checked that