Dominque, We put together a quick C program to try out the C API a few weeks ago, it worked but it was very slow, from memory not much different to the sqlite command line backup system. We put it on the back burner as it wasn?t anywhere near quick enough.
We hadn?t seen or found or even looked for RBU, when I read this I thought Realtime Backup Unit, I wasn?t even close :) Rats I think that unless we can get the C API to back up in a time close to that of a cp, the easiest solution is to suspend updates for 10-15 mins out-of-hours and do a simple cp from there. Sometimes a change in workflow might be the easiest and simplest solution. I know you have mentioned VFS shims further down the email trail but thats certainly a step too far for us. Thanks Rob On 4 May 2016, at 12:22, Dominique Devienne wrote: > On Wed, May 4, 2016 at 1:13 PM, Rob Willett > <rob.sqlite at robertwillett.com> wrote: >> Thanks for the reply, >> >> Yes Example 2 in https://www.sqlite.org/backup.html is what we are >> talking >> about. It was very slow to run for us. > > Then maybe https://www.sqlite.org/rbu.html is your last change. > Although I don't see how it could be faster than the Backup API. > > I think you should share more details of how you use the Backup API, > so experts can provide advice on what to try to make it scale better. > --DD > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
