Home
last modified time | relevance | path

Searched refs:writer (Results 1 – 24 of 24) sorted by relevance

/sqlite-3.40.0/ext/fts2/
H A Dfts2.c1211 DLWriter writer; in docListMerge() local
1277 dlwDestroy(&writer); in docListMerge()
1315 PLWriter writer; in posListUnion() local
1356 DLWriter writer; in docListUnion() local
1411 PLWriter writer; in posListPhraseMerge() local
1465 DLWriter writer; in docListPhraseMerge() local
1502 DLWriter writer; in docListAndMerge() local
1537 DLWriter writer; in docListOrMerge() local
1587 DLWriter writer; in docListExceptMerge() local
5278 LeafWriter writer; in segmentMerge() local
[all …]
/sqlite-3.40.0/ext/fts5/
H A Dfts5_index.c4173 pWriter->writer.pgno = 1; in fts5WriteInit()
4195 pWriter->writer.buf.n = 4; in fts5WriteInit()
4319 writer.writer.pgno = pSeg->pgnoLast+1; in fts5IndexMergeLevel()
4320 writer.iBtPage = 0; in fts5IndexMergeLevel()
4383 fts5BufferAppendVarint(&p->rc, &writer.writer.buf, 0); in fts5IndexMergeLevel()
4385 fts5BufferAppendVarint(&p->rc, &writer.writer.buf, 0); in fts5IndexMergeLevel()
4391 fts5BufferAppendVarint(&p->rc, &writer.writer.buf, nPos); in fts5IndexMergeLevel()
4544 Fts5SegWriter writer; member
4592 Fts5SegWriter writer; in fts5FlushOneHash() local
4595 pBuf = &writer.writer.buf; in fts5FlushOneHash()
[all …]
H A Dfts5_expr.c497 Fts5PoslistWriter writer = {0}; in fts5ExprSynonymList() local
514 rc = sqlite3Fts5PoslistWriterAppend(pBuf, &writer, iMin); in fts5ExprSynonymList()
545 Fts5PoslistWriter writer = {0}; in fts5ExprPhraseIsMatch() local
606 rc = sqlite3Fts5PoslistWriterAppend(&pPhrase->poslist, &writer, iPos); in fts5ExprPhraseIsMatch()
657 Fts5PoslistWriter writer; /* Writer context */ member
743 Fts5PoslistWriter *pWriter = &a[i].writer; in fts5ExprNearIsMatch()
2857 Fts5PoslistWriter writer; member
2936 &pExpr->apExprPhrase[i]->poslist, &p->aPopulator[i].writer, p->iOff in fts5ExprPopulatePoslistsCb()
/sqlite-3.40.0/test/
H A De_walckpt.test306 # Close first the reader, then later the writer. Give up before
315 # Close first the writer, then later the reader. And finally the
390 # Open a writer. Write a transaction. Then begin, but do not commit,
457 # The reader and writer have now dropped their locks. And so a
480 # TRUNCATE modes also obtain the exclusive "writer" lock on the
491 # busy-handler callback) until there is no database writer and all
494 # The test below shows that both the reader and writer have
499 # they release the reader and writer transactions in different
502 # EVIDENCE-OF: R-60642-04082 If the writer lock cannot be obtained
504 # writer lock retried until either the busy-handler returns 0 or the
[all …]
H A Dthread005.test82 # One thread is a reader and the other thread a reader and a writer. The
83 # writer thread repeats the following transaction as fast as possible:
105 # executed by the writer adds a row with "b IS NULL" to the table, but
111 # writer was executing the UPDATE statement, then it could incorrectly
H A Dwalblock.test65 # the writer finishes.
70 # call made by the writer between updating the two copies of the
H A Dbackup.test488 # 1) Backing up file-to-file. The writer writes via an external pager.
489 # 2) Backing up file-to-file. The writer writes via the same pager as
495 foreach {writer file} {db test.db db3 test.db db :memory:} {
522 execsql { UPDATE t1 SET a = a + 1 } $writer
551 } $writer
568 execsql { VACUUM } $writer
588 } $writer
627 } $writer
H A Dwritecrash.test12 # Test the outcome of a writer crashing within a call to the VFS
H A Dsnapshot3.test31 # file - using a writer or a "PRAGMA wal_checkpoint = TRUNCATE" - while
H A Dwal5.test256 # 1. The writer lock: FULL and RESTART checkpoints block until any writer
H A Dwal9.test13 # been fixed. The problem occurred if a writer process with a subset
H A Dwal2.test81 # Two connections are established to the database file - a writer ([db])
85 # 1. Modify the database using the writer.
399 lappend expected_locks {0 1 lock exclusive} ;# Lock writer
412 lappend expected_locks {0 1 unlock exclusive} ;# Unlock writer
H A Dwal3.test349 # that a writer has written to the log. In this case the reader should
496 # wal-index header and the lock was obtained that a writer has
H A Dwal.test58 # wal-2.*: Test MVCC with one reader, one writer.
514 # database via [db]. This should fail (writer lock cannot be obtained).
626 # At one point, if a reader failed to upgrade to a writer because it
H A Dlock.test145 # connections, because UNIX supports reader/writer locks. Under windows,
H A Dexclusive.test178 # locked out as a writer.
H A Dwalthread.test288 # writer may cause the dedicated checkpoint thread to return an
H A Dfts1porter.test23440 writer writer
23441 writers writer
/sqlite-3.40.0/src/
H A Dvdbesort.c1560 memset(&writer, 0, sizeof(PmaWriter)); in vdbeSorterListToPMA()
1585 vdbePmaWriterInit(pTask->file.pFd, &writer, pTask->pSorter->pgsz, in vdbeSorterListToPMA()
1588 vdbePmaWriteVarint(&writer, pList->szPMA); in vdbeSorterListToPMA()
1591 vdbePmaWriteVarint(&writer, p->nVal); in vdbeSorterListToPMA()
1592 vdbePmaWriteBlob(&writer, SRVAL(p), p->nVal); in vdbeSorterListToPMA()
1596 rc = vdbePmaWriterFinish(&writer, &pTask->file.iEof); in vdbeSorterListToPMA()
1886 PmaWriter writer; in vdbeIncrPopulate() local
1896 i64 iEof = writer.iWriteOff + writer.iBufEnd; in vdbeIncrPopulate()
1904 vdbePmaWriteVarint(&writer, nKey); in vdbeIncrPopulate()
1905 vdbePmaWriteBlob(&writer, pReader->aKey, nKey); in vdbeIncrPopulate()
[all …]
H A Dsqlite.h.in9371 ** database writer and all readers are reading from the most recent database
9381 ** that the next writer will restart the log file from the beginning.
9383 ** database writer attempts while it is pending, but does not impede readers.
9407 ** exclusive "writer" lock on the database file. ^If the writer lock cannot be
9409 ** the writer lock retried until either the busy-handler returns 0 or the lock
9412 ** the writer lock is obtained or while waiting for database readers, the
/sqlite-3.40.0/doc/
H A Dvfs-shm.txt63 only one reader or one writer or one checkpointer could be active at a
65 a single state equivalent to READ, meaning that a writer could
H A Dwal-lock.md48 A database writer must obtain the exclusive WRITER lock. It uses a blocking
/sqlite-3.40.0/ext/async/
H A DREADME.txt76 steady stream that exceeds the I/O capability of the background writer
/sqlite-3.40.0/ext/fts5/test/
H A Dfts5porter.test11728 writer writer writers writer