Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Merge fixes from the 3.23 branch. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
cc22fb914a1b70059c5e40334ec016f3 |
| User & Date: | drh 2018-05-09 10:11:28 |
Context
|
2018-05-17
| ||
| 20:40 | Updates to the change log and other documentation pages. (check-in: 4c3f0e6adb user: drh tags: trunk) | |
|
2018-05-09
| ||
| 10:11 | Merge fixes from the 3.23 branch. (check-in: cc22fb914a user: drh tags: trunk) | |
| 10:10 | Fix documentation typos. (check-in: 9d89e82c5d user: drh tags: trunk) | |
|
2018-04-30
| ||
| 22:39 | More detail on synchronous=NORMAL. (check-in: 13c3dff046 user: drh tags: branch-3.23) | |
Changes
Changes to pages/pragma.in.
1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 |
most commonly used synchronous setting when not in [WAL mode].</dd>
<dt><b>NORMAL</b> (1)</dt>
<dd>
^When synchronous is NORMAL (1), the SQLite database
engine will still sync at the most critical moments, but less often
than in FULL mode. There is a very small (though non-zero) chance that
a power failure at just the wrong time could corrupt the database in
NORMAL mode. But in practice, you are more likely to suffer
a catastrophic disk failure or some other unrecoverable hardware
fault. Many applications choose NORMAL when in [WAL mode].</dd>
<dt><b>OFF</b> (0)</dt>
<dd>
^With synchronous OFF (0), SQLite continues without syncing
as soon as it has handed data off to the operating system.
If the application running SQLite crashes, the data will be safe, but
the database [cfgerrors|might become corrupted] if the operating system
crashes or the computer loses power before that data has been written
|
| | > > > > > > | |
1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 |
most commonly used synchronous setting when not in [WAL mode].</dd>
<dt><b>NORMAL</b> (1)</dt>
<dd>
^When synchronous is NORMAL (1), the SQLite database
engine will still sync at the most critical moments, but less often
than in FULL mode. There is a very small (though non-zero) chance that
a power failure at just the wrong time could corrupt the database in
[journal_mode]=DELETE on an older filesystem.
[WAL mode] is safe from corruption with synchronous=NORMAL, and probably
DELETE mode is safe too on modern filesystems. WAL mode is always consistent
with synchronous=NORMAL, but WAL mode does lose durability. A transaction
committed in WAL mode with synchronous=NORMAL might roll back following
a power loss or system crash. Transactions are durable across application
crashes regardless of the synchronous setting or journal mode.
The synchronous=NORMAL setting is a good choice for most applications
running in [WAL mode].</dd>
<dt><b>OFF</b> (0)</dt>
<dd>
^With synchronous OFF (0), SQLite continues without syncing
as soon as it has handed data off to the operating system.
If the application running SQLite crashes, the data will be safe, but
the database [cfgerrors|might become corrupted] if the operating system
crashes or the computer loses power before that data has been written
|