Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Typo, fixes #3170. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
67eb1e7a66f240fd916431f2cc8dc18b |
| User & Date: | mihailim 2008-06-25 06:35:11 |
Context
|
2008-06-25
| ||
| 06:43 | Fixed #3019. check-in: f12d719b3c user: mihailim tags: trunk | |
| 06:35 | Typo, fixes #3170. check-in: 67eb1e7a66 user: mihailim tags: trunk | |
|
2008-06-23
| ||
| 11:16 | Fix typo identified by cvstrac ticket #3136. check-in: 84ce96a21d user: dan tags: trunk | |
Changes
Changes to pages/lockingv3.in.
316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 |
<ol>
<li>Make sure all rollback journal data has actually been written to
the surface of the disk (and is not just being held in the operating
system's or disk controllers cache) so that if a power failure occurs
the data will still be there after power is restored.</li>
<li>Obtain a PENDING lock and then an EXCLUSIVE lock on the database file.
If other processes are still have SHARED locks, the writer might have
to wait until those SHARED locks clear before it is able to obtain
an EXCLUSIVE lock.</li>
<li>Write all page modifications currently held in memory out to the
original database disk file.</li>
</ol>
<p>
|
| |
316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 |
<ol>
<li>Make sure all rollback journal data has actually been written to
the surface of the disk (and is not just being held in the operating
system's or disk controllers cache) so that if a power failure occurs
the data will still be there after power is restored.</li>
<li>Obtain a PENDING lock and then an EXCLUSIVE lock on the database file.
If other processes still have SHARED locks, the writer might have
to wait until those SHARED locks clear before it is able to obtain
an EXCLUSIVE lock.</li>
<li>Write all page modifications currently held in memory out to the
original database disk file.</li>
</ol>
<p>
|