Akonadi/Postgres update - KDE UserBase Wiki
Jump to content
From KDE UserBase Wiki
This page contains
changes
which are not marked for translation.
Other languages:
українська
This guide describes the steps to follow in order to upgrade your Akonadi database when using the PostgreSQL backend.
In order to use this guide, you need to have both the old and new PostgreSQL versions installed.
The applications paths mentioned below are valid for openSUSE users. You may have to adapt these paths for your distribution.
The
initdb
and
pg_upgrade
tools are required. Make sure these applications are available before following this guide. In openSUSE
pg_upgrade
is part of the
postgresql-contrib
package.
Stop the Akonadi services
akonadictl stop
(wait until all the akonadi processes are gone)
Create an extra backup
cp -R $HOME/.local/share/akonadi/db_data $HOME/.local/share/akonadi/db_data_15
Rename the Akonadi database directory
mv $HOME/.local/share/akonadi/db_data $HOME/.local/share/akonadi/db_data_old
Create the new database, using the postgreSQL 16 executable
/usr/lib/postgresql16/bin/initdb --pgdata=$HOME/.local/share/akonadi/db_data --encoding=UTF-8 --data-checksums --no-locale
Check if upgrading is safe
/usr/lib/postgresql16/bin/pg_upgrade -b /usr/lib/postgresql15/bin -B /usr/lib/postgresql16/bin -d $HOME/.local/share/akonadi/db_data_old -D $HOME/.local/share/akonadi/db_data --check
For more details about this command, you may read the
pg_upgrade
documentation.
If pg_upgrade doesn't detect any problem, you can start the database upgrade
/usr/lib/postgresql16/bin/pg_upgrade -b /usr/lib/postgresql15/bin -B /usr/lib/postgresql16/bin -d $HOME/.local/share/akonadi/db_data_old -D $HOME/.local/share/akonadi/db_data
Last steps, starting akonadi
akonadictl start
and running the consistency check
akonadictl fsck
After checking that your applications work as usual, you may delete the two backup copies you created earlier.
More Information
openSUSE Leap 15.2: Akonadi fails to start after upgrading to PostgreSQL 12 with the same error as in
. Workaround: Install PostgreSQL 11, set it as default (with
update-alternatives
), and upgrade to PostgreSQL 11.
Upgrading PostgreSQL
(Arch linux wiki)
Upgrading PostgreSQL
(Official PostgreSQL documentation)
Retrieved from "