Hi,
I noticed an interesting disk-space behavior with VACUUM. If I vacuum my 
places.sqlite(Firefox database), it's 49mb. If then copy my 2 biggest 
tables with
  CREATE table2 as select * from orig_table; drop table ; alter table2 
rename to table;

Then vacuum, the db becomes 24mb. The same behavior occurs if I use the 
create statement from sqlite_master to setup the copy-table.

Is this a bug or expected behavior?

Thanks,
Taras
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to