*** 8,13 **** --- 8,32 ---- and ticket #2224. ---- + **Fixed In Version 3.4.1:** + + A feature was introduced in version 3.3.14 that avoids + flushing the database page cache if nothing in the database + has changed. This feature depends on a change counter in + the header of the database file being incremented whenever + the file is modified. + + Unfortunately, a bug causes the VACUUM command to reset + the change counter back to zero rather than increment it. + So if two connections A and B have the database open and + cached and the change counter happens to be at zero, and + one connection changes the database then vacuums, the + other connection will not see the change. It will use an + obsolete cache. This might lead to corruption. + + This is an unlikely scenario. We have never actually + observed it to occur in the wild. We discovered the + problem while doing a code analysis due to ticket #2518. **Fixed In Version 3.4.0 (2007-06-15):**
Small. Fast. Reliable.
Choose any three.
Choose any three.
|
|