On 13 Apr 2011, at 4:36pm, James Green wrote: > On 13 April 2011 15:33, Simon Slavin <slav...@bigfraud.org> wrote: >> >> On 13 Apr 2011, at 12:14pm, James Green wrote: >> >>> sync=full does not work well for our app (no transactions). Far too slow. >> >> If you're not syncing, then section 3.2 of the page Richard probably >> indicates what's causing your corruption. > > Without a reset or power loss? This is the bit that's causing concern.
Actually I'm now persuaded that everyone else is right, and that this may not be causing your problem. >> So for a while, leave that PRAGMA alone, accept that you're going to get >> slow running, and see whether this makes the corruption go away. If it does >> then you can tackle the speed problem separately without worrying about data >> corruption. > > This is the approach we will be rolling out. More specifically we'll > be trying synchronous=normal. It will likely take a few days before we > can roll this out and evaluate. ... nevertheless, this might be a worthwhile test. Whether this makes everything work normally or not it could tell you at what level your data is getting corrupted. Another useful test might be to run integrity checking without waiting for any obvious corruption. In all these things take Richard's advice over mine, of course. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
