Bug 511652 - Feature: Drop Akonadi database and re-sync again but keep current configurations
Summary: Feature: Drop Akonadi database and re-sync again but keep current configurations
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 6.5.2
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-04 22:37 UTC by sourcemaker
Modified: 2025-11-06 23:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description sourcemaker 2025-11-04 22:37:49 UTC 
Is there a safe method to drop the entire Akonadi database and resynchronize everything without losing the current configurations?
Comment 1 Allen Winter 2025-11-05 20:05:13 UTC 
I wonder if an upgrade to newer postgres that we don't current properly support is causing all the problems with your upgrade.
it really can't be akonadi itself.

https://wiki.archlinux.org/title/KDE  see section "4.4.1.2 PostgreSQL" might have some hints

also there was some discussion related to akonadi+postgres17 at https://bugs.kde.org/show_bug.cgi?id=507899 that might trigger some ideas.

beyond pointing you to some other web pages there's not much I can do to help as I know nothing about the backend databases.
Comment 2 sourcemaker 2025-11-05 21:26:08 UTC 
I've been using PostgreSQL 18 for days and it worked flawlessly before the update.
I'll take a look at your links right away.
Comment 3 sourcemaker 2025-11-06 23:03:31 UTC 
My last attempt: Nuke Akonadi and reconfigure everything was also unsuccessful.
The problems persist.