1 |
On Thursday 12 Nov 2015 04:48:49 J. Roeleveld wrote: |
2 |
> On 11 November 2015 23:07:41 CET, Mick <michaelkintzios@×××××.com> wrote: |
3 |
> >On Wednesday 11 Nov 2015 20:28:07 Marc Joliet wrote: |
4 |
> >> On Wednesday 11 November 2015 20:37:24 J. Roeleveld wrote: |
5 |
> >> >I saw plenty of errors with mysql. |
6 |
> >> > |
7 |
> >> >After switching to Postgresql, they seem to have disappeared. |
8 |
> >> |
9 |
> >> FWIW, I use mariadb myself, which is also the virtual/mysql default |
10 |
> >> provider, last I checked. |
11 |
> >> |
12 |
> >> Greetings |
13 |
> > |
14 |
> >@Mark: Yes, same here, but the errors are produced by mariadb too. |
15 |
> > |
16 |
> >@Joost: Is postgresql starting as a process by akonadi, or are you |
17 |
> >running it |
18 |
> >independently and pointing akonadi to it? |
19 |
> > |
20 |
> >PS. I read somewhere that if mysql is running independently of akonadi, |
21 |
> >then |
22 |
> >the akonadi errors/corruptions are fewer, or not happen at all. |
23 |
> |
24 |
> As I use Postgresql also for other stuff, it's started seperately. |
25 |
> |
26 |
> I also found this performs better, having it run "embedded" only had a |
27 |
> slightly better performance when compared to mysql (or mariadb, don't |
28 |
> remember) "embedded". |
29 |
> |
30 |
> A framework like akonadi should, IMO, also be able to be run on a server |
31 |
> with clients connecting to there to allow different machines to all use |
32 |
> the same data. |
33 |
> |
34 |
> The current solution makes running with a shared home and logged in from |
35 |
> different clients simultaneously problematic (to say the least) |
36 |
> |
37 |
> -- |
38 |
> Joost |
39 |
|
40 |
Can you please explain how you have akonadi configured to use an existing db |
41 |
instance? Did you have to set up an akonadi db user and passwd? |
42 |
-- |
43 |
Regards, |
44 |
Mick |