On 7 Dec 2009, at 10:31pm, raf wrote: > Simon Slavin wrote: > >> On 7 Dec 2009, at 9:58pm, Chris Eich wrote: >> >>> On my Linux platform, I find that the INSERT >>> INTO archive.my_table SELECT * FROM my_table WHERE (...) takes unreasonably >>> long (it involves about 30MB of data). >> >> Do you have a transaction around all the INSERT commands ? This will speed >> it up many fold. > > there aren't multiple insert commands. > only a single insert command was mentioned. > it would be a single transaction already. > > i have no advice, i'm just pointing out that > this advice seems to be based on the false > assumption that multiple transactions are > involved (because this is the most common > reason why things slow down).
You're quite right. I missed that entirely. I have no idea if the second piece of advice (DROP INDEXes, add records, reCREATE INDEXes) will help. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
