Maybe this for this scenario: You have in-memory database, used mostly for reading and you want to save its copy to disk when update on in-memory is performed? Otherwise, what is copied and what is to write in "copy on write"?
________________________________________ From: sqlite-users [sqlite-users-boun...@mailinglists.sqlite.org] on behalf of Keith Medcalf [kmedc...@dessus.com] Sent: Friday, October 04, 2019 12:19 PM To: SQLite mailing list Subject: Re: [sqlite] Copy-on-write VFS On Friday, 4 October, 2019 05:18, Fredrik Larsen <frel...@gmail.com> wrote: >A copy-on-write IO-path where data is split into static and dynamic parts >(think snapshots for storage) would be very helpful for our project, . What do you mean? Useful how? >This would simplify backups, testing, moving data around in a multinode >environment, etc. Since we still do not know what you are on about, then this is debatable. >Does something like this exist for sqlite? In my head this sounds like an >relative easy feature to add as IO-stuff is already centralized in the >VFS layer. Maybe a new COW-VFS? Still do not know exactly what you are on about. Can you explain what you are on about? -- 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 https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmailinglists.sqlite.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsqlite-users&data=02%7C01%7Croman.fleysher%40einstein.yu.edu%7C9ef1d96d7e3840552f4208d748e6ad65%7C04c70eb48f2648079934e02e89266ad0%7C1%7C1%7C637058027904564324&sdata=8hS93ORYmBXeRHKt4bF4di3AOQswyKWSzvjIGPInDBY%3D&reserved=0 _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
