Hi Dan, thanks for the tips.
the strace tip did the trick. I discovered that the problem was not in the index creation but in the database creation. it seems that during DB creation, a certain commit failed due to Disk quota and after that indexing failed. strangely I don't understand this disk consumption problem I got. a question I have, given the fact that I have a 64 M DB with a promary key on an integer column (which means that implicit index is being done), what are my overall disk requirements, any rule of thumbs here ? many thanks Tal On 12/10/2011 06:01 AM, Tal Tabakman wrote: >* Hi,*>**>* thanks for the reply.*>**>* so, I don't have TMPDIR defined in my >env. what is the behaviour of*>* sqlite in such cases ? is there a default ?* By default it will try /var/tmp, then /usr/tmp, then /tmp. SQLite creates temporary files there that it uses to sort the data before creating the index. This is different from the database journal file, which is created in the same directory as the database file. You say in another post that the db is only 64MB in size. So I guess it is not too likely that you are running out of temp space. Still, try setting TMPDIR to something sensible anyway. Another way to go is to run the whole thing under [strace]. Then inspect the output and see if there is an unexpected system call failure towards the end. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
