Documentation Source Text

Check-in [ecd3254d36]
Login

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

Overview
Comment:Fix requirement mark errors in the cache_spill pragma docs.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: ecd3254d3678bf323362cad6c1ac7c3390a10cf9
User & Date: drh 2015-12-03 22:34:31
Context
2015-12-09
11:51
Merge the revised sponsor icon layout into trunk. check-in: 7251ac0674 user: drh tags: trunk
2015-12-08
22:28
Experiment with a new look for the homepage and especially the layout of sponsor links. check-in: f96d1199e7 user: drh tags: new-sponsors-layout
2015-12-03
22:34
Fix requirement mark errors in the cache_spill pragma docs. check-in: ecd3254d36 user: drh tags: trunk
22:05
Merge the AUTOINCREMENT typo fix from the 3.9 branch. check-in: 3dec493cba user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/pragma.in.

246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
    should leave it that way as cache spilling is usually advantageous.
    However, a cache spill has the side-effect of acquiring an
    [EXCLUSIVE lock] on the database file.  Hence, some applications that
    have large long-running transactions may want to disable cache spilling
    in order to prevent the application from acquiring an exclusive lock
    on the database until the moment that the transaction [COMMIT]s.
    <p>^(The "PRAGMA cache_spill=<i>N</i>" form of this pragma sets a minimum
    cache size threshold required for spilling to occur.  The number of pages
    in cache must exceed both the cache_spill threshold and the maximum cache
    size set by the [PRAGMA cache_size] statement in order for spilling to
    occur.  
    <p>^(The "PRAGMA cache_spill=<i>boolean</i>" form of this pragma applies
    across all databases attached to the database connection.  But the
    "PRAGMA cache_spill=<i>N</i>" form of this statement only applies to
    the "main" schema or whatever other schema is specified as part of the
    statement.
}

Pragma cache_size {
    <p>^(<b>PRAGMA DB.cache_size;
       <br>PRAGMA DB.cache_size = </b><i>pages</i><b>;
       <br>PRAGMA DB.cache_size = -</b><i>kibibytes</i><b>;</b></p>
    <p>Query or change the suggested maximum number of database disk pages







|


|

|


|







246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
    should leave it that way as cache spilling is usually advantageous.
    However, a cache spill has the side-effect of acquiring an
    [EXCLUSIVE lock] on the database file.  Hence, some applications that
    have large long-running transactions may want to disable cache spilling
    in order to prevent the application from acquiring an exclusive lock
    on the database until the moment that the transaction [COMMIT]s.
    <p>^(The "PRAGMA cache_spill=<i>N</i>" form of this pragma sets a minimum
    cache size threshold required for spilling to occur.)^ ^(The number of pages
    in cache must exceed both the cache_spill threshold and the maximum cache
    size set by the [PRAGMA cache_size] statement in order for spilling to
    occur.)^
    <p>^(The "PRAGMA cache_spill=<i>boolean</i>" form of this pragma applies
    across all databases attached to the database connection.)^  ^(But the
    "PRAGMA cache_spill=<i>N</i>" form of this statement only applies to
    the "main" schema or whatever other schema is specified as part of the
    statement.)^
}

Pragma cache_size {
    <p>^(<b>PRAGMA DB.cache_size;
       <br>PRAGMA DB.cache_size = </b><i>pages</i><b>;
       <br>PRAGMA DB.cache_size = -</b><i>kibibytes</i><b>;</b></p>
    <p>Query or change the suggested maximum number of database disk pages