Re: Sqlite akonadi transaction mode fix
On Thursday 22 January 2015 12:11:09 Martin Steigerwald wrote:
> Am Donnerstag, 22. Januar 2015, 12:05:40 schrieb Martin Steigerwald:
> > Am Donnerstag, 22. Januar 2015, 10:39:38 schrieb David Goodenough:
> > > On Thursday 22 January 2015 10:50:53 Martin Steigerwald wrote:
> > > > Am Mittwoch, 21. Januar 2015, 09:49:18 schrieb David Goodenough:
> > > > > I use KdePIM and thus akonadi with SqLite. I am running unstable
> > > > > and
> > > > > am
> > > > > up to date with fixes.
>
> […]
>
> > > > > Looking in the KDE bug database I found:-
> > > > >
> > > > > http://osdir.com/ml/kde-commits/2014-07/msg02228.html
> > > > >
> > > > > which seems to address the repeated dialog boxes I get while filters
> > > > > run
> > > > > on
> > > > > my mailboxes, and the log messages of which:-
> > > > >
> > > > > DATABASE ERROR:
> > > > > Error code: 6
> > > > > DB error: "database is deadlocked"
> > > > > Error text: "database is deadlocked Unable to fetch row"
> > > > > Query: "UPDATE PimItemTable SET atime = ? WHERE ( (
> > > > > PimItemTable.id
> > > > > =
> > > > > ?
> > > > > )
> > > > >
> > > > > )"
> > > > >
> > > > > is an example. All the errors I get currently are deadlock errors.
> > > > >
> > > > > I don't think this fix is in the current build, and I realise that
> > > > > Debian
> > > > > is getting ready for a new release and thus it is unlikely that this
> > > > > fix
> > > > > will be able to be slotted in any time soon. Can I simply get the
> > > > > source, add this one patch and rebuild, or is it more complicated.
> > > > > Also
> > > > > which package(s) would I have to rebuild? Is it just
> > > > > akonadi-backend-sqlite?
> > > >
> > > > I read again and again, that KDEPIM developers themselves recommend
> > > > not
> > > > to
> > > > use SQLite backend. I used PostgreSQL backend for some time, but now
> > > > use
> > > > MySQL backend as I believe it is most widely tested. But AFAIK as
> > > > least
> > > > one
> > > > KDEPIM developers uses the PostgreSQL backend. It has the disadvantage
> > > > tough that on major PostgreSQL updates you have to dump and restore
> > > > the
> > > > database to upgrade its structures.
> > > >
> > > > I compiled akonadi and kdepim myself quite some time, but not from
> > > > package,
> > > > but installed it to /usr/local and initialized it with some
> > > > environment
> > > > variable settings. Its all described on kde wiki sites.
> > > >
> > > > As to using Debian packages: Well basically its grab the source,
> > > > change,
> > > > rebuild. You would need quite some build dependencies satisfied, but
> > > > you
> > > > need that either way. The turn around time would be higher than just
> > > > compiling and installing with make install I think, but I bet you
> > > > wouldn´t
> > > > need to do this often.
> > > >
> > > > That said, I didn´t rebuild KDEPIM related packages yet, but I did
> > > > this
> > > > with Digikam and it worked quite nice.
> > > >
> > > > As for updates to Debian packages, I´d like to see current akonadi
> > > > 1.13
> > > > branch packages, cause it contains quite some noticeable performance
> > > > updates regarding database access that made MySQL disappear from cpu
> > > > usage
> > > > top for most of the time. Its really a huge difference.
> > > >
> > > > I use c733429f4fa9696fb027ddc946e54f6bbb68deaf of Akonadi git repo on
> > > > two
> > > > of my systems for at least a month and it works nice.
> > > >
> > > > And well if what you point to is really a fix, I bet it may be
> > > > cherry-picked for the package. But if you can verify first, that the
> > > > fix
> > > > works, I think chances are higher to convince a Debian Qt/KDE team
> > > > member
> > > > to merge the change. So your idea of testing it locally by compiling
> > > > yourself makes sense to me.
> > >
> > > I am happy to do this, what I was trying to find out was exactly which
> > > packages I would need to rebuild - does akonadi-backend-sqlite seem
> > > right?
> > > or am I going to have to rebuild the whole of kdepim?
> >
> > You need to rebuild the akonadi source package:
> >
> > merkaba:~> apt-cache show akonadi-backend-sqlite
> > Package: akonadi-backend-sqlite
> > Source: akonadi
> >
> > As I use a self-compiled akonadi 1.13 branch together with KDEPIM as
> > packaged in Debian Sid currently, there shouldn´t be an issue.
> >
> > Heck, you can even just try to compile and install into /usr/local,
> > without
> > building a package using the approach I have shown in my other mail.
> >
> > You would need to sent the cmake variable for the database backend
> > accordingly. I have
> >
> > DATABASE_BACKEND MYSQL
> >
> > there.
> >
> > if trying to compile from Git 1.13 branch. But that would get you the
> > database optimizations as well that I have been testing over the last
> > months. I think they are in the generic database code, so may benefit the
> > SQLite backend as well.
>
> Well okay, and you need the sqlite devel stuff installed. For reference here
> is the complete cmake config I use:
>
> AKONADI_BUILD_QSQLITE ON
> AKONADI_BUILD_TESTS ON
> BUILD_TESTING ON
> CMAKE_BUILD_TYPE
> CMAKE_COMPILE_GCOV OFF
> CMAKE_INSTALL_PREFIX /usr/local
> DATABASE_BACKEND MYSQL
> INSTALL_QSQLITE_IN_QT_PREFIX OFF
> LIB_SUFFIX
> MYSQLD_EXECUTABLE /usr/sbin/mysqld
> POSTGRES_PATH POSTGRES_PATH-NOTFOUND
> QT5_BUILD OFF
> QT_QMAKE_EXECUTABLE /usr/bin/qmake-qt4
> SQLITE_LINK_STATIC OFF
> SQLITE_STATIC_LIBRARIES /usr/lib/x86_64-linux-gnu/libsqlite3.a
> STATIC_LIBRARY OFF
> UPDATE_MIME_DATABASE_EXECUTABL /usr/bin/update-mime-database
> WITH_SOPRANO OFF
> XMLLINT_EXECUTABLE /usr/bin/xmllint
> XSLTPROC_EXECUTABLE /usr/bin/xsltproc
>
> the compile is basically a:
>
> - git clone of the repo
> - mkdir build
> - cd build
> - cmake ..
> - ccmake .. (to adapt settings, can also do with cmake -D if you know which
> vars to set)
> - make -j4 (adjust to amount of CPU cores)
> - sudo make install
>
> (do it all somewhere in your home directory and only use root for the last
> step)
>
> Removing it is a bit more complicated, as cmake doesn´t produce an uninstall
> target for the make file. I use:
>
> ~/KDE/Dev/akonadi/build> cat install_manifest.txt | xargs rm
>
> install_manifest.txt has which files it installed with complete path.
>
> Ciao,
Thank you, I will give it a go. Not quite sure when (I have my mother's
to organise next week) but I will report back when I have done so.
David
Reply to: