Akonadi dsaster

Martin Steigerwald martin at lichtvoll.de
Tue Oct 11 13:54:07 BST 2016

Am Dienstag, 11. Oktober 2016, 11:54:45 CEST schrieb Diederik de Haas:
> On dinsdag 11 oktober 2016 11:03:16 CEST Martin Steigerwald wrote:
> > I also switched to MariaDB, but whether that makes sense… it works at
> > least.
> > 
> > I do think Akonadi as a background service in general makes sense, whether
> > a  MySQL database is the best way to store the metadata… I am not so sure
> > about.
> I use PostgreSQL as the backend on my main PC and that works rather well,
> although still not perfect.
> On my laptop I used the default, thus MySQL (in its default configuration)
> and that works considerably less, while only handling a part of my mail
> accounts.
> At some (near?) point in time I will switch to PostgreSQL on my laptop too
> and my guess is that there's a real good chance that it would improve
> Akonadi's working considerably.
> There is one downside to using PostgreSQL as Dan explained in [1].
> But once you've figured out a proper procedure for it [2], it's actually
> straight forward

Thank you for the links. I am aware of Dan using PostgreSQL. I used it once 
myself. Even system-wide for a while, but also user-wide. With PostgreSQL I 
dislike that on major upgrade you need to migrate your database AFAIK. I see 
the links are exactly about this. Thank you for the pointer!

Also I meant my comment more generally. I think the user of KDEPIM should not 
need to administrate and probably manually tune a relational database. Heck, 
this is mail, calendaring and so… so I think it would be beneficial to store 
the metadata with some database or tool that doesn´t need manual maintenance 
or tuning at all. Not every KMail user is also a DB administrator.

> [1] http://www.dvratil.cz/2016/01/kde-pim-still-alive-and-rocking/
> #comment-1861
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838732


More information about the kdepim-users mailing list