Yesterday I upgraded my Mastodon instance to go from PostgreSQL 15 PostgreSQL 17.
Uncategorized
5
Posts
3
Posters
0
Views
-
Yesterday I upgraded my Mastodon instance to go from PostgreSQL 15 PostgreSQL 17. The whole process was so simple that it almost seems silly to blog about it, but I did it anyway, in case anyone is interested:
https://blog.thms.uk/2025/06/upgrade-postgres-15-17-mastodon?utm_source=mastodon
Special thanks to @ruud who told me about link mode in
pg_upgradeclusterwhich was the missing piece I needed in oder to get the upgrade done with my limited disk space. -
Yesterday I upgraded my Mastodon instance to go from PostgreSQL 15 PostgreSQL 17. The whole process was so simple that it almost seems silly to blog about it, but I did it anyway, in case anyone is interested:
https://blog.thms.uk/2025/06/upgrade-postgres-15-17-mastodon?utm_source=mastodon
Special thanks to @ruud who told me about link mode in
pg_upgradeclusterwhich was the missing piece I needed in oder to get the upgrade done with my limited disk space.Tried to upgrade #postgresql for my oldfriends.live #Mastodon ( @paul ) instance from 13 to 18 and got incompatible_polymorphics errors following @michael guide. Can anyone offer advice?
The error is:
In database: postgres
aggregate: repack.array_accum(anyelement)
In database: mastodon_production
aggregate: repack.array_accum(anyelement) -
Tried to upgrade #postgresql for my oldfriends.live #Mastodon ( @paul ) instance from 13 to 18 and got incompatible_polymorphics errors following @michael guide. Can anyone offer advice?
The error is:
In database: postgres
aggregate: repack.array_accum(anyelement)
In database: mastodon_production
aggregate: repack.array_accum(anyelement)@FeedingTubePaul @paul @ruud There's a reason why my guide goes to v17 rather than v18 ๐ฌ
This does sound like pg_repack is your problem though. Maybe uninstall it?
-
@FeedingTubePaul @paul @ruud There's a reason why my guide goes to v17 rather than v18 ๐ฌ
This does sound like pg_repack is your problem though. Maybe uninstall it?
@michael Still failing after repack removed.
Do you think I need to
DROP AGGREGATE repack.array_accum(anyelement);for both postgres and mastodon_production databases.
If so, I need to figure out the best way to do that from the debian terminal.
I hate database upgrades.
-
@michael Still failing after repack removed.
Do you think I need to
DROP AGGREGATE repack.array_accum(anyelement);for both postgres and mastodon_production databases.
If so, I need to figure out the best way to do that from the debian terminal.
I hate database upgrades.
@FeedingTubePaul @michael @ClearlyClaire
i *think* you can have it on both db even if you uninstalled pg_repack
Gli ultimi otto messaggi ricevuti dalla Federazione
-
In 2025 AI still requires you to watch it do it's work and catch it early before it goes fully off the rails, like driving a Tesla. That's impossible in the github UI. It doesn't help that the MS engineers are shit a prompting ("tests are failing, please fix" is way way too vague) but the whole idea of doing it through github is doomed from the start.
-
Dammit Robin, get your head on straight!!
-
I think this means "yes", and also, the source is available! I knew GEOS for C64 and C128 was floating around out there somewhere, didn't know the PC version also got liberated.
-
Non ho mai capito il successo di WhatsApp. Telegram รจ molto piรน performante eppure รจ meno usato.
-
@rizard ๐
-
PC GEOS or GeoWorks could run on 8088, right? I wonder if it runs on PCjr... I was always curious about it, but didn't own a PC when it was relevant. My first PC was Windows 95 era, and it soon got Red Hat Linux.
That's also part of why it failed, I think? They wrote much of it in assembler and going to 32-bit architecture while competing with a much better funded Microsoft and Apple was a challenge maybe?
-
-
Questa settimana niente palestra. La mia testa mi sta dicendo chiaramente che mai piรน. Allenarmi non รจ piรน solo una questione di massa grassa e magra.
