Akonadi-upgrade to postgres 17 fails

Axel Braun axel.braun at gmx.de
Thu Aug 7 10:38:54 BST 2025


Hello Ingo,

Am Donnerstag, 7. August 2025, 11:09:36 Mitteleuropäische Sommerzeit schrieb Ingo Klöcker:
> On Montag, 4. August 2025 07:39:11 Mitteleuropäische Sommerzeit Axel Braun 
> wrote:
> > Good morning,
> > I wanted to upgrade akonadi to pg 17, following
> > https://userbase.kde.org/Akonadi/Postgres_update
> > 
> > The first steps worked fine, the upgrade check fails:
> > 
> > axel at southpole:~> /usr/lib/postgresql17/bin/pg_upgrade -b
> > /usr/lib/postgresql16/bin -B /usr/lib/postgresql17/bin -d
> > $HOME/.local/share/akonadi/db_data_old -D
> > $HOME/.local/share/akonadi/db_data --check Führe Konsistenzprüfungen durch
> > -------------------------------
> > Checking cluster versions                                     ok
> > 
> > der alte Cluster verwendet keine Datenprüfsummen, aber der neue verwendet
> > sie Fehlgeschlagen, Programm wird beendet
> > 
> > 
> > Translation: The old cluster does not use checksums, the new one does.
> > 
> > How can I work around this?
> 
> You need to remove the --data-checksums option from the initdb call to create 
> the new cluster without data checksums.

Sure, that is an option. But I guess many more users will step into that trap, as the wiki was changed to use this option
 
> Alternatively, disable data checksums in the already created new cluster with
> /usr/lib/postgresql17/bin/pg_checksums -d -D $HOME/.local/share/akonadi/
> db_data
> 
> Finally, if you want to use data checksums then you can enable data checksums 
> on the old cluster with the pg_checksums helper. Read the man page of 
> pg_checksums for details.

Tried that, but failed - see https://bugs.kde.org/show_bug.cgi?id=507899

Finally I tried to convert to sqlite backend, but that throws an error as well:
Should be https://bugs.kde.org/show_bug.cgi?id=493393

CHeers
Axel




More information about the kdepim-users mailing list