| 1 |
On Thursday 12 Nov 2015 08:05:52 J. Roeleveld wrote: |
| 2 |
> On Thursday, November 12, 2015 07:30:49 AM Mick wrote: |
| 3 |
> > On Thursday 12 Nov 2015 04:48:49 J. Roeleveld wrote: |
| 4 |
> > > On 11 November 2015 23:07:41 CET, Mick <michaelkintzios@×××××.com> |
| 5 |
wrote: |
| 6 |
> > > >On Wednesday 11 Nov 2015 20:28:07 Marc Joliet wrote: |
| 7 |
> > > >> On Wednesday 11 November 2015 20:37:24 J. Roeleveld wrote: |
| 8 |
> > > >> >I saw plenty of errors with mysql. |
| 9 |
> > > >> > |
| 10 |
> > > >> >After switching to Postgresql, they seem to have disappeared. |
| 11 |
> > > >> |
| 12 |
> > > >> FWIW, I use mariadb myself, which is also the virtual/mysql default |
| 13 |
> > > >> provider, last I checked. |
| 14 |
> > > >> |
| 15 |
> > > >> Greetings |
| 16 |
> > > > |
| 17 |
> > > >@Mark: Yes, same here, but the errors are produced by mariadb too. |
| 18 |
> > > > |
| 19 |
> > > >@Joost: Is postgresql starting as a process by akonadi, or are you |
| 20 |
> > > >running it |
| 21 |
> > > >independently and pointing akonadi to it? |
| 22 |
> > > > |
| 23 |
> > > >PS. I read somewhere that if mysql is running independently of |
| 24 |
> > > >akonadi, then |
| 25 |
> > > >the akonadi errors/corruptions are fewer, or not happen at all. |
| 26 |
> > > |
| 27 |
> > > As I use Postgresql also for other stuff, it's started seperately. |
| 28 |
> > > |
| 29 |
> > > I also found this performs better, having it run "embedded" only had a |
| 30 |
> > > slightly better performance when compared to mysql (or mariadb, don't |
| 31 |
> > > remember) "embedded". |
| 32 |
> > > |
| 33 |
> > > A framework like akonadi should, IMO, also be able to be run on a |
| 34 |
> > > server with clients connecting to there to allow different machines to |
| 35 |
> > > all use the same data. |
| 36 |
> > > |
| 37 |
> > > The current solution makes running with a shared home and logged in |
| 38 |
> > > from different clients simultaneously problematic (to say the least) |
| 39 |
> > > |
| 40 |
> > > -- |
| 41 |
> > > Joost |
| 42 |
> > |
| 43 |
> > Can you please explain how you have akonadi configured to use an existing |
| 44 |
> > db instance? Did you have to set up an akonadi db user and passwd? |
| 45 |
> |
| 46 |
> Yes. |
| 47 |
> You need to create a user with password on the database where akonadi can |
| 48 |
> create the tables. |
| 49 |
> |
| 50 |
> Here is my akonadi-config: |
| 51 |
> *** |
| 52 |
> % cat .config/akonadi/akonadiserverrc |
| 53 |
> [%General] |
| 54 |
> Driver=QPSQL |
| 55 |
> |
| 56 |
> [QPSQL] |
| 57 |
> Name=joost-akonadi |
| 58 |
> Host=localhost |
| 59 |
> Options= |
| 60 |
> ServerPath=/usr/bin/pg_ctl |
| 61 |
> InitDbPath=/usr/bin/initdb |
| 62 |
> StartServer=false |
| 63 |
> User=<username> |
| 64 |
> Password=<password> |
| 65 |
> Port=5432 |
| 66 |
> |
| 67 |
> [Debug] |
| 68 |
> Tracer=null |
| 69 |
> |
| 70 |
> *** |
| 71 |
> |
| 72 |
> It also works with the database running on a different machine. |
| 73 |
> |
| 74 |
> -- |
| 75 |
> Joost |
| 76 |
|
| 77 |
Thank you Joost. Did you export/import akonadi databases when you moved over |
| 78 |
from MySQL, or was it not necessary? |
| 79 |
|
| 80 |
One of the databases contains calendar data and I do not want to cause loss of |
| 81 |
it. |
| 82 |
-- |
| 83 |
Regards, |
| 84 |
Mick |
Archives