Documentation Source Text

Check-in [633d838aa0]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix another howtocorrupt.html typo.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | branch-3.22
Files: files | file ages | folders
SHA3-256: 633d838aa070d2adf83d84b7e6774d22aa40499a0b9771a24f4625f60bbfdfcf
User & Date: drh 2018-01-31 02:53:43.960
Context
2018-02-01
14:43
Fix a typo in the flattening rules of the optoverview.html document. (check-in: 20ecb45b42 user: drh tags: branch-3.22)
2018-01-31
02:53
Fix another howtocorrupt.html typo. (check-in: 633d838aa0 user: drh tags: branch-3.22)
02:52
Typo in the how-to-corrupt document. (check-in: 6ad1abb448 user: drh tags: branch-3.22)
Changes
Side-by-Side Diff Ignore Whitespace Patch
Changes to pages/howtocorrupt.in.
︙
528
529
530
531
532
533
534
535

536
537
538
539

528
529
530
531
532
533
534

535
536
537
538
539








-
+





of recovery because the previous process writing to it crashed in the
middle of a transaction and two or more processes try to open the 
that database at the same time, then the race condition might cause
one of those processes to get a false indication that the recovery 
has already completed, allowing that process to continue using the
database file without running recovery first.  If that process writes
to the file, then the file might go corrupt.  This race condition
had apparently existing in all prior versions of SQLite for Windows going
had apparently existed in all prior versions of SQLite for Windows going
back to 2004.  But the race was very tight.  Practically speaking, you
need a fast multi-core machine in which you launch two processes to run
recovery at the same moment on two separate cores.  This defect was
on Windows systems only and did not affect the posix OS interface.</p>