0
0
mirror of https://github.com/sqlite/sqlite.git synced 2024-11-29 00:12:23 +01:00
sqlite/test/walpersist.test
drh 28f32bedd1 It turns out that pagerExclusiveLock() can be called with the lock state
already set to RESERVED if the SQLITE_FCNTL_PERSIST_WAL setting is set and
a specific sequence of multiple journal mode changes occur.
Enhance pagerExclusiveLock() to deal with this.
[forum:/forumpost/8130545bc6|Forum post 8130545bc6]

FossilOrigin-Name: 2bb8d977392f635515aa4a36f6f763a2e4858f7adc1120519e2e74c04a9749b5
2023-05-07 03:23:32 +00:00

143 lines
3.4 KiB
Plaintext

# 2011 July 26
#
# The author disclaims copyright to this source code. In place of
# a legal notice, here is a blessing:
#
# May you do good and not evil.
# May you find forgiveness for yourself and forgive others.
# May you share freely, never taking more than you give.
#
#***********************************************************************
#
# This file contains tests for using WAL with persistent WAL file mode.
#
set testdir [file dirname $argv0]
source $testdir/tester.tcl
source $testdir/lock_common.tcl
set ::testprefix walpersist
ifcapable !wal {
finish_test
return
}
do_test walpersist-1.0 {
db eval {
PRAGMA journal_mode=WAL;
CREATE TABLE t1(a);
INSERT INTO t1 VALUES(randomblob(5000));
}
file exists test.db-wal
} {1}
do_test walpersist-1.1 {
file exists test.db-shm
} {1}
do_test walpersist-1.2 {
db close
list [file exists test.db] [file exists test.db-wal] [file exists test.db-shm]
} {1 0 0}
do_test walpersist-1.3 {
sqlite3 db test.db
db eval {SELECT length(a) FROM t1}
} {5000}
do_test walpersist-1.4 {
list [file exists test.db] [file exists test.db-wal] [file exists test.db-shm]
} {1 1 1}
do_test walpersist-1.5 {
file_control_persist_wal db -1
} {0 0}
do_test walpersist-1.6 {
file_control_persist_wal db 1
} {0 1}
do_test walpersist-1.7 {
file_control_persist_wal db -1
} {0 1}
do_test walpersist-1.8 {
file_control_persist_wal db 0
} {0 0}
do_test walpersist-1.9 {
file_control_persist_wal db -1
} {0 0}
do_test walpersist-1.10 {
file_control_persist_wal db 1
} {0 1}
do_test walpersist-1.11 {
db close
list [file exists test.db] [file exists test.db-wal] [file exists test.db-shm]
} {1 1 1}
# Make sure the journal_size_limit works to limit the size of the
# persisted wal file. In persistent-wal mode, any non-negative
# journal_size_limit causes the WAL file to be truncated to zero bytes
# when closing.
#
forcedelete test.db test.db-shm test.db-wal
do_test walpersist-2.1 {
sqlite3 db test.db
db eval {
PRAGMA journal_mode=WAL;
PRAGMA wal_autocheckpoint=OFF;
PRAGMA journal_size_limit=12000;
CREATE TABLE t1(x);
INSERT INTO t1 VALUES(randomblob(50000));
UPDATE t1 SET x=randomblob(50000);
}
expr {[file size test.db-wal]>100000}
} {1}
do_test walpersist-2.2 {
file_control_persist_wal db 1
db close
concat [file exists test.db-wal] [file size test.db-wal]
} {1 0}
do_test walpersist-2.3 {
sqlite3 db test.db
execsql { PRAGMA integrity_check }
} {ok}
do_test 3.1 {
catch {db close}
forcedelete test.db test.db-shm test.db-wal
sqlite3 db test.db
execsql {
PRAGMA page_size = 1024;
PRAGMA journal_mode = WAL;
PRAGMA wal_autocheckpoint=128;
PRAGMA journal_size_limit=16384;
CREATE TABLE t1(a, b, PRIMARY KEY(a, b));
}
} {wal 128 16384}
do_test 3.2 {
for {set i 0} {$i<200} {incr i} {
execsql { INSERT INTO t1 VALUES(randomblob(500), randomblob(500)) }
}
file_control_persist_wal db 1
db close
} {}
do_test walpersist-3.3 {
file size test.db-wal
} {0}
do_test walpersist-3.4 {
sqlite3 db test.db
execsql { PRAGMA integrity_check }
} {ok}
# 2023-05-07 https://sqlite.org/forum/forumpost/8130545bc6
#
reset_db
do_test 4.1 {
db eval {
PRAGMA journal_mode=WAL;
CREATE TABLE t1(x);
}
file_control_persist_wal db 1
db eval {
PRAGMA journal_mode=TRUNCATE;
PRAGMA journal_mode=MEMORY;
PRAGMA journal_mode=WAL;
PRAGMA journal_mode=PERSIST;
}
} {truncate memory wal persist}
finish_test