On Apr 14, 2009, at 6:33 AM, Dan wrote: > > On Apr 14, 2009, at 4:00 PM, Bjorn Toft Madsen wrote: > >> Hi, >> >> The docs for SQLite state: >> - Situations Where Another RDBMS May Work Better >> - Very large datasets >> - [...] [sqlite] has to allocate a bitmap of dirty pages in the >> disk file to help it manage its rollback journal. [...] >> >> Aside from a larger page size, what remedies are suggested for >> removing (or minimizing) this requirement? > > That statement is out of date. Since it was written the bitmap has > been replaced with a better data structure that does not require the > big per-transaction allocation. >
Right. The change to get rid of that bitmap happened over a year ago. (That change also made transactions run a little faster, which was a surprising, though welcomed, side-effect.) Unfortunately, I failed to update the documentation referenced above. I have just now checked in a fix to the documentation. It now reads that one should consider a different database engine if you are contemplating databases larger than 2 tebibytes in size. SQLite should scale up to that size now, assuming you have a disk-drive and filesystem that can hold a file that big. D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
