SQlite backend series updated
nicolas.s-dev at laposte.net
Wed Mar 30 18:28:06 BST 2011
On Tue, Mar 29, 2011 at 12:07:06AM -0400, Sebastian Spaeth wrote:
> I know that some people want this, so I worked on the sqlite branch and
> it works now for me.
> The reason for using sqlite is that we currently rewrite the
> (potentially some MB large) LocalStatus cache for every modification
> that we perform. By default we first write to a tmp file, call fsync,
> move to final location and call fsync again. For every change. This
> hurts when someone has very large maildirs.
> I won't propose this series for inclusion in this cycle, although it is
> optional and configurable (off by default). There is more
> than enough new stuff in this release, I guess, so I don't send the
> patch series, but you can grab it from the feature/sqlite-LocalStatus
> branch in my offlineimap repository. I tested it, and it works for me.
Merged into pu.
> The feature is optional and can be configured by setting
> status_backend=sqlite in the local [Repository ...] section. (Yes, it
> makes probably more sense in the [Account ...] section, doesn't it ?).
It does FMPOV.
> When using it, it will create a new folder
> ~/.offlineimap/Account-XXX/LocalStatus-sqlite next to the existing
> ~/.offlineimap/Account-XXX/LocalStatus folder (which it will leave
> untouched, so that has to be removed manually if people want to switch
Good for now.
> Note, that there is still a potentially large plain text file mapping
> UIDs when you sync IMAP<->IMAP which I haven't touched yet.
> This builds on the original patches by Stewart Smith and Rob Browning
> but has been modified quite a bit.
They should be granted in the related commit messages.
More information about the OfflineIMAP-project