Documentation Source Text

Check-in [006ea9f849]
Login

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

Overview
Comment:One of the disadvantages of WAL mode is that one cannot change the page_size.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 006ea9f849ebb23611f168bef302769f1c9a5e45
User & Date: drh 2016-09-13 22:45:37
Context
2016-09-13
23:54
Add links to android bindings, SDS, and Fossil to the documentation lists. check-in: e581a20834 user: drh tags: trunk
22:45
One of the disadvantages of WAL mode is that one cannot change the page_size. check-in: 006ea9f849 user: drh tags: trunk
22:40
Version 3.14.2 check-in: bf7ce59b7b user: drh tags: trunk, release, version-3.14.2
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/wal.in.

53
54
55
56
57
58
59

60
61
62
63
64
65
66
<li>There is an additional quasi-persistent "<tt>-wal</tt>" file and
    "<tt>-shm</tt>" shared memory file associated with each
    database, which can make SQLite less appealing for use as an 
    [application file-format].
<li>There is the extra operation of [checkpointing] which, though automatic
    by default, is still something that application developers need to
    be mindful of.

<li><s>WAL works best with smaller transactions.  WAL does
    not work well for very large transactions.  For transactions larger than
    about 100 megabytes, traditional rollback journal modes will likely
    be faster.  For transactions in excess of a gigabyte, WAL mode may 
    fail with an I/O or disk-full error.
    It is recommended that one of the rollback journal modes be used for
    transactions larger than a few dozen megabytes.</s>







>







53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
<li>There is an additional quasi-persistent "<tt>-wal</tt>" file and
    "<tt>-shm</tt>" shared memory file associated with each
    database, which can make SQLite less appealing for use as an 
    [application file-format].
<li>There is the extra operation of [checkpointing] which, though automatic
    by default, is still something that application developers need to
    be mindful of.
<li>The [page_size] of the database file cannot be changed while in WAL mode.
<li><s>WAL works best with smaller transactions.  WAL does
    not work well for very large transactions.  For transactions larger than
    about 100 megabytes, traditional rollback journal modes will likely
    be faster.  For transactions in excess of a gigabyte, WAL mode may 
    fail with an I/O or disk-full error.
    It is recommended that one of the rollback journal modes be used for
    transactions larger than a few dozen megabytes.</s>