> Currently if an interrupt
> arrives during a long commit I have no way to know whether the commit
> was successful, and thus whether to commit or roll back the filesystem
> journal.
Maybe you can read the database to see if the new data
is there in this scenario.
> If I could flush the dirty
Hello,
I'm looking for a way to force sqlite to do its internal "phase one
commit", which apparently flushes dirty pages to disk without committing
the journal. This way I can minimize the time spent in the "phase two
commit", which is the point at which the journal is unlinked and the
2 matches
Mail list logo
