> I think that the PRAGMA for auto-vacuum might be the right thing for your > situation. Unfortunately it would have to be done before any tables were > created. The simplest way to do this for a database which already exists > might be to use the shell tool to dump the existing database to SQL > statements, create a new database, do the PRAGMA, then read the data into the > new database.
You can also run VACUUM after changing auto-vacuum mode. It will apply new auto-vacuum mode to a re-created database. Pavel On Mon, Apr 23, 2012 at 10:01 AM, Simon Slavin <[email protected]> wrote: > > On 23 Apr 2012, at 2:25pm, Max Vlasov <[email protected]> wrote: > >> On Mon, Apr 23, 2012 at 3:35 PM, Simon Slavin <[email protected]> wrote: >>> >>> For the second one, the simplest way to do something like defragment the >>> data inside the file is to use the VACUUM command: >> >> Simon, thanks, I see what vacuum can do, sure I use it frequently as >> many of us. Ironically when I noticed the slowness, I did VACUUM that >> took almost a half an hour alone because the db contained other >> persistent data including big indexes. I think handling free list >> alone (for example allowing sort them only with a pragma) would help >> in cases like mine but unfortunately will add more confusion. > > I think that the PRAGMA for auto-vacuum might be the right thing for your > situation. Unfortunately it would have to be done before any tables were > created. The simplest way to do this for a database which already exists > might be to use the shell tool to dump the existing database to SQL > statements, create a new database, do the PRAGMA, then read the data into the > new database. > > Simon. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
