[kdepim-users] changing database backend

[René J.V. Bertin]

On Wednesday November 12 2014 13:40:44 Daniel Vrátil wrote:

>I personally use PostgreSQL, because I find it faster and more reliable. At 
>some point I'd like to see it as default backend (but that's another topic). I 
>can't say how well PostgreSQL performs on OS X, and I think you will be more 

I must have been unclear - my idea of changing concerned my Linux rigs because those run on ZFS.
You're undoubtedly aware that you disable COW on btrfs (I suppose for performance reasons). That's highly "not done" on ZFS and thus impossible, but also much less necessary because of internal optimisation (or so I have been told). Either way, it makes sense to disable COW-like features in software when it write to a filesystem that already implements it. MySQL allows that by setting innodb_doublewrite=0 .
I'd compare the other option but 1) I'd have to start the server myself and 2) no way if I'd have to redo the whole of akonadi again...

>lucky with getting some support for MariaDB on OS X than PostgreSQL, but I 

FYI, mariadb works "out of the box" with MacPorts.

>to use the new backend, and start it. Yes, this is the only case when we 
>actually recommend wiping Akonadi :)

What's funny with that? :P Yes, I found that out though I did manage to restore old agent_config files from a backup. A simple DB change actually seemed to work out fine, but for some reason I started having "ghost accounts" showing up only in KMail and in terminal output. They did correspond to rc files that were left after I'd tested accounts and removed others to recreate them - housekeeping apparently isn't akonadi's strong point. After the restore I only had a "Local Folders" resource showing up in akonadiconsole, but that one's gone after I had to do a powercycle for some hopefully unrelated reason.

René

_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users