On Saturday, 5 October, 2019 15:44, Kadirk <kadirkaracel...@gmail.com> wrote:
>How to do online backup of an in memory database (to disk)? An in memory database is a transient object. Why would you want to back it up? >Planning to use in memory database with 10 gb+ data, there are queries >continuously so stopping application is not an option. And how does queries cause problems? Reading is reading and you can be reading as much as you like simultaneously. Rather than queries do you mean updates? If so, this brings back the original question: why are you storing something which is transient in nature to persistent storage -- or more correctly why are you using an inherently transient structure to store persistent data? >Looks like for on disk databases it is possible with a non-blocking >fashion but I couldn't find a way to do it for in memory database. >Whenever an update comes in, backup process starts over so it won't >finish. Any idea how to solve this? Are you using the sqlite3_serialize interfaces to serialize the in memory database? Once you have an additional copy of the database in memory, you can simply write it to a disk file. https://sqlite.org/c3ref/serialize.html -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
