Documentation Source Text

Check-in [a8e5cf50a0]
Login

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

Overview
Comment:Clarification of the automerge documentation in FTS3.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: a8e5cf50a044253c78104615183e63684c0b8f83
User & Date: drh 2014-07-07 13:13:30
Context
2014-07-18
19:06
Clarify that PRAGMA wal_autocheckpoint always causes a PASSIVE checkpoint. Provide clearer definitions for PASSIVE, FULL, and RESET checkpoints. check-in: 306698cb1d user: drh tags: trunk
2014-07-07
13:13
Clarification of the automerge documentation in FTS3. check-in: a8e5cf50a0 user: drh tags: trunk
10:39
Add documentation for the "^" qualifier to fts3.html. check-in: 6a74a13c86 user: dan tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/fts3.in.

1996
1997
1998
1999
2000
2001
2002

2003
2004

2005
2006
2007
2008
2009
2010
2011
  quickly, which may speed up full-text queries and, if the workload 
  contains UPDATE or DELETE operations as well as INSERTs, reduce the space
  on disk consumed by the full-text index. However, it also increases the
  amount of data written to disk.

<p>
  For general use in cases where the workload contains few UPDATE or DELETE

  operations, is 8. If the workload contains many UPDATE or DELETE commands, 
  or if query speed is a concern, it may be advantageous to reduce it to 2.


<p>
  For reasons of backwards compatibility, the "automerge=1" command sets
  the automerge parameter to 8, not 1 (a value of 1 would make no sense 
  anyway, as merging data from a single segment is a no-op).









>
|
|
>







1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
  quickly, which may speed up full-text queries and, if the workload 
  contains UPDATE or DELETE operations as well as INSERTs, reduce the space
  on disk consumed by the full-text index. However, it also increases the
  amount of data written to disk.

<p>
  For general use in cases where the workload contains few UPDATE or DELETE
  operations, a good choicd for automerge is 8. If the workload contains
  many UPDATE or DELETE commands, 
  or if query speed is a concern, it may be advantageous to reduce automerge
  to 2.

<p>
  For reasons of backwards compatibility, the "automerge=1" command sets
  the automerge parameter to 8, not 1 (a value of 1 would make no sense 
  anyway, as merging data from a single segment is a no-op).