On 11 November 2015 23:07:41 CET, Mick <michaelkintz...@gmail.com> wrote: >On Wednesday 11 Nov 2015 20:28:07 Marc Joliet wrote: >> On Wednesday 11 November 2015 20:37:24 J. Roeleveld wrote: >> >I saw plenty of errors with mysql. >> > >> >After switching to Postgresql, they seem to have disappeared. >> >> FWIW, I use mariadb myself, which is also the virtual/mysql default >> provider, last I checked. >> >> Greetings > >@Mark: Yes, same here, but the errors are produced by mariadb too. > >@Joost: Is postgresql starting as a process by akonadi, or are you >running it >independently and pointing akonadi to it? > >PS. I read somewhere that if mysql is running independently of akonadi, >then >the akonadi errors/corruptions are fewer, or not happen at all.
As I use Postgresql also for other stuff, it's started seperately. I also found this performs better, having it run "embedded" only had a slightly better performance when compared to mysql (or mariadb, don't remember) "embedded". A framework like akonadi should, IMO, also be able to be run on a server with clients connecting to there to allow different machines to all use the same data. The current solution makes running with a shared home and logged in from different clients simultaneously problematic (to say the least) -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
