diff options
| author | Carlos Garnacho <carlosg@gnome.org> | 2018-09-30 12:48:25 +0200 |
|---|---|---|
| committer | Carlos Garnacho <carlosg@gnome.org> | 2018-09-30 12:55:37 +0200 |
| commit | 46043ac52387cd6dc9c677f9580dfd4720245c86 (patch) | |
| tree | ec8c18afa53ea6346852a5d2b7180c640c9b544e | |
| parent | df01997d187587793b98d06d56ff8aa9e3ee8a7d (diff) | |
| download | tracker-46043ac52387cd6dc9c677f9580dfd4720245c86.tar.gz | |
libtracker-direct: Ignore error on passive WAL checkpoint
The sqlite3_wal_checkpoint_v2() docs don't seem very clear on
whether SQLITE_BUSY may be returned on passive checkpoints (In
fact, I seem to read the opposite).
But that seems to happen in practice. Since a passive checkpoint
is failable in essence, just ignore the error.
| -rw-r--r-- | src/libtracker-direct/tracker-direct.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/libtracker-direct/tracker-direct.c b/src/libtracker-direct/tracker-direct.c index 7a26f2064..3dee1bc8b 100644 --- a/src/libtracker-direct/tracker-direct.c +++ b/src/libtracker-direct/tracker-direct.c @@ -193,7 +193,9 @@ wal_checkpoint (TrackerDBInterface *iface, GError *error = NULL; g_debug ("Checkpointing database..."); - tracker_db_interface_sqlite_wal_checkpoint (iface, blocking, &error); + + tracker_db_interface_sqlite_wal_checkpoint (iface, blocking, + blocking ? &error : NULL); if (error) { g_warning ("Error in WAL checkpoint: %s", error->message); |