-------------------------------------------- >El lun, 10/2/14, Simon Slavin <slav...@bigfraud.org> escribió: > > Asunto: Re: [sqlite] Free Page Data usage > Para: "General Discussion of SQLite Database" <sqlite-users@sqlite.org> > Fecha: lunes, 10 de febrero, 2014 12:34 > > > On 10 Feb 2014, at 11:29am, Raheel Gupta <raheel...@gmail.com> > wrote: > > >>> 64-bit page numbers would not be backwards > compatible. > > > > It might be possible to implement it in backwards > compatible mode. I guess > > SQlite has some free flags in its superblock. Maybe we > can use a single > > byte to mark that this is a 64 bit page number ? > > The problem is that people would create a file in the new > version of SQLite which could handle 64 bits, and expect to > be able to open it in old versions of SQLite which would not > understand it. > > It would seem that the move from SQLite3 to SQLite4 would be > a good time to make all file pointers 64 bits. But I > don't know enough about the internal workings of SQLite4 to > know for sure. > > Simon.
Sqlite4 is a completly different beast. It uses a hashmap & reduce. I don't see any improvement moving sqlite3 to 64 bits page number neither. The problem about inner fragmentation, using 64 KB page size is solved if, from time to time, make a backup, close db and open backup as main db file. If db is very huge, backup and switch will cost time, and a DBMS where indexes/indexs, db statistics, tables, etc... are split in several files, I mean, Postgresql, SQLServer, etc... may work better ( inner fragmentation point of view ) and should be used. HTH _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
