Hi, Yes the files sizes of "test.db", "test.db-wal" and "test.db-shm" are 1024, 4333512 and 65536 bytes respectively as specified below.
Most of the test scripts are failing when the -shm file size grows from 32kb to 64kb (though the "test.db-wal" file size varies for different test scripts). But there are cases in WAL tests where the size increases to 64kb, but the problem is not seen. Is there any problem while allocating/increasing shared memory, or is the WAL page indexes getting corrupted when shared memory increases? Please suggest some tips to find out the root cause for this issue. Thanks, Praveen ________________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] On Behalf Of Dan Kennedy [danielk1...@gmail.com] Sent: Saturday, October 02, 2010 2:39 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] TestFixture 3.7.2 - Some WAL tests fail on QNX OS On Oct 1, 2010, at 2:20 PM, Raj, Praveen wrote: > Hi, > > I'm validating SQLite test suite version 3.7.2 on QNX operating > system. I have built the testfixture using SQLite amalgation file > and other related files/libraries. > > I ran the full test suite and most of the test cases are passing, > except some run in journal_mode = WAL. Test cases whose > autocheckpoint is turned off and large amount of > data is being inserted without checkpointing are failing. Other WAL > tests are passing. I tried increasing the stack size of the > testfixture process, but that didn't help. > > If i reduce the number of inserts or increase the WAL page size, > test cases are passing. I believe there is some corruption happening > with the WAL index while > inserting large number of rows. Here is an example (from SQLite test > suite) of the failure > (Purposefully added "PRAGMA integrity_check" at end of wal3-1.0) How large are the "test.db", "test.db-wal" and "test.db-shm" files on your system after the transaction in wal3-1.0? i.e. stick puts [file size test.db] puts [file size test.db-wal] puts [file size test.db-shm] or similar after the test case. Here the files are 1024, 4333512 and 65536 bytes. From what you are saying it sounds like the problem is occurring when the -shm file grows from 32KB to 64KB. Dan. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
