[GRASS-user] turning sqlite journal off
laura.poggio at gmail.com
Thu May 16 01:28:20 PDT 2019
thanks for the answers and apologies if my question at the beginning was
not so clear.
SQLITE can support multiple readers and only one writer. But it is not the
The issue here is the creation of the journal file. Each time a GRASS
session that modified the sqlite.db file is closed, the journal file is
created. This can take quite some time and during this time the database is
locked. This behaviour is expected.
I can turn off the creation of the journal file (being aware of the
potential risks) using sqlite options and thus reducing the time the
database is locked. However these options do not apply when the file is
modified by GRASS.
Is it possible to turn off the creation of the journal file when a GRASS
session is involved?
On Thu, 16 May 2019 at 00:07, Nikos Alexandris <nik at nikosalexandris.net>
> * Markus Metz <markus.metz.giswork at gmail.com> [2019-05-15 22:55:13 +0200]:
> >On Tue, May 14, 2019 at 11:12 AM Panagiotis Mavrogiorgos <
> pmav99 at gmail.com>
> >> Hi Laura,
> >> This thread seems to be related:
> >> I also had a somewhat similar problem that was related to the VACUUM
> >command issued when closing a GRASS session (new session started before
> >VACUUM of the previous session was finished)
> >> If I understand this correctly, you are not supposed to concurrently use
> >the same sqlite database.
> >Yes, this is a limitation of sqlite, and the GRASS-internal sqlite driver
> >has been adapted accordingly as much as possible.
> Nevertheless, concurrent reading is allowed. Reading the discussion so
> far, one may think that no concurrent use is possible at all.
> See also https://sqlite.org/whentouse.html :
> "SQLite supports an unlimited number of simultaneous readers, but it
> will only allow one writer at any instant in time."
> And in https://sqlite.org/lockingv3.html see 'SHARED'.
> Also, https://stackoverflow.com/a/4060838/1172302.
> grass-user mailing list
> grass-user at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-user