Re: Akonadi-upgrade to postgres 17 fails
Axel Braun <[email protected]> Thu, 07 Aug 2025 11:38:54 +0200
| Newsgroups | gmane.comp.kde.users.pim |
|---|---|
| Message-ID | <4917486.JiC3Le5eUH@p1> |
Hello Ingo, Am Donnerstag, 7. August 2025, 11:09:36 Mitteleurop=C3=A4ische Sommerzeit s= chrieb Ingo Kl=C3=B6cker: > On Montag, 4. August 2025 07:39:11 Mitteleurop=C3=A4ische Sommerzeit Axel= Braun=20 > wrote: > > Good morning, > > I wanted to upgrade akonadi to pg 17, following > > https://userbase.kde.org/Akonadi/Postgres_update > >=20 > > The first steps worked fine, the upgrade check fails: > >=20 > > axel@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=C3=BChre Konsistenzpr=C3= =BCfungen durch > > ------------------------------- > > Checking cluster versions ok > >=20 > > der alte Cluster verwendet keine Datenpr=C3=BCfsummen, aber der neue ve= rwendet > > sie Fehlgeschlagen, Programm wird beendet > >=20 > >=20 > > Translation: The old cluster does not use checksums, the new one does. > >=20 > > How can I work around this? >=20 > You need to remove the --data-checksums option from the initdb call to cr= eate=20 > the new cluster without data checksums. Sure, that is an option. But I guess many more users will step into that tr= ap, as the wiki was changed to use this option =20 > 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 >=20 > Finally, if you want to use data checksums then you can enable data check= sums=20 > on the old cluster with the pg_checksums helper. Read the man page of=20 > pg_checksums for details. Tried that, but failed - see https://bugs.kde.org/show_bug.cgi?id=3D507899 =46inally I tried to convert to sqlite backend, but that throws an error as= well: Should be https://bugs.kde.org/show_bug.cgi?id=3D493393 CHeers Axel