Lines Matching full:power
212 ** and the fact that the page size must be a power of 2.
376 ** SQLITE_POW2_MEMORY_SIZE // internal power-of-two allocator
1542 ** of 8. Some allocators round up to a larger multiple or to a power of 2.
1693 ** (a power of two between 512 and 32768) plus a little extra for each
5741 ** be allocated by the cache. ^szPage will not be a power of two. ^szPage
13839 ** 1. All memory allocations sizes are rounded up to a power of 2.
13851 ** allocation size (after rounding all sizes up to a power of 2.) Let M
13872 ** size of the array is a power of 2.
13874 ** The size of this object must be a power of two. That fact is
14054 int iFullSz; /* Size of allocation rounded up to power of 2 */
14067 ** power of two that we can represent using 32-bit signed integers.
14073 /* Round nByte up to the next valid power of two */
14077 ** block. If not, then split a block of the next larger power of
14199 ** memsys5Round(). Hence nBytes is always a non-negative power
14232 ** All allocations must be a power of two and must be expressed by a
14277 /* The size of a Mem5Link object must be a power of two. Verify that
18845 /* 1.0e+22 is the largest power of 10 than can be
23281 ** (2) An application crash or power loss can leave stale lock files
24464 ** or power failure will likely corrupt the database file.
24551 ** If we do not do this and we encounter a power failure, the directory
29290 ** Should be a power of 2, and ideally, evenly divide into BITVEC_USIZE.
31553 ** This could conceivably cause corruption following a power failure on
31774 ** checking information. If the power fails while the journal is being
31776 ** file after power is restored. If an attempt is then made
32210 ** power failure in this case anyway.
32349 ** are within range. To be 'in range', both values need to be a power
32795 ** If journal corruption occurs due to a power failure, the most likely
32883 ** thought. If a power
32928 ** journal. Otherwise, a power loss might leave modified data in the
33270 ** value of nRec from the size of the journal file. But if a power
33279 ** no-sync option for the journal. A power failure could lead to corruption
33281 ** deleted when the power is restored) we don't care.
33622 ** or power failures by changing the number of syncs()s when writing
33631 ** that an inopertune power failure could leave the journal
33752 ** * the new page size (value of *pPageSize) is valid (a power
34070 ** be played back into the database. If a power failure occurs while
34163 ** previous connections transaction), and a crash or power-failure
35750 ** an integer power of 2. It sets variable pg1 to the identifier
36850 ** "no such page". The page size can be any power of 2 between 512 and 32768.
39819 ** an abrupt power failure when synchronous is off, the database
39835 ** how well the database resists damage due to OS crashes and power
39873 ** The page size must be a power of 2 between 512 and 65536. If the page
39877 ** Page sizes are constrained to be a power of two so that the region
40735 ** and populated with enough information so that if a power loss occurs
58944 ** The size chosen is a little less than a power of two. That way,
58946 ** a power-of-two allocation. This mimimizes wasted space in power-of-two
102315 ** "new_size" must be a power of 2. The hash table might fail
