/ Timeline
Login

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

34 check-ins tagged with "readonly-wal-recovery"

2017-11-14
03:42
Improvement to a comment. No changes to code. Closed-Leaf check-in: 486949fc user: drh tags: readonly-wal-recovery
2017-11-13
05:51
Remove some branches in walTryBeginRead() that were added by check-in [ce5d13c2de] but became unreachable with the addition of logic in check-in [18b26843] that enabled read-only clients to parse the WAL file into a heap-memory WAL-index, thus guaranteeing that the WAL-index header is always available. check-in: 9c6b38b9 user: drh tags: readonly-wal-recovery
2017-11-11
20:11
In wal.c: improved comments, new assert() and testcase() macros, and replace some magic numbers with appropriate symbolic constants. check-in: 13ec8a77 user: drh tags: readonly-wal-recovery
13:30
Further comment improvements in wal.c. No code changes. check-in: 34638800 user: drh tags: readonly-wal-recovery
2017-11-10
20:00
Improved comments and variable names in the read-only WAL logic. check-in: d3c25740 user: drh tags: readonly-wal-recovery
2017-11-09
23:24
Avoid superfluous SHM unlock call in the Win32 VFS. check-in: 5a384be6 user: mistachkin tags: readonly-wal-recovery
22:25
Cleanup superfluous whitespace changes. check-in: a2908e2c user: mistachkin tags: readonly-wal-recovery
22:23
Revise and vastly simplify the Win32 SHM file locking semantics, allowing all new tests to pass. check-in: d0997b0f user: mistachkin tags: readonly-wal-recovery
20:37
Add an assert() in the Win32 VFS. check-in: 22e58330 user: mistachkin tags: readonly-wal-recovery
20:34
Enhance walro2.test to better ensure that readonly_shm clients are not using invalid *-shm files. check-in: ff630b66 user: dan tags: readonly-wal-recovery
20:02
Get read-only SHM file tests passing on Win32. check-in: abef0535 user: mistachkin tags: readonly-wal-recovery
18:53
Further corrections to read-only SHM file handling on Win32. check-in: 43c31170 user: mistachkin tags: readonly-wal-recovery
18:21
Corrections to Win32 lock detection for SHM files. check-in: 3a91be97 user: mistachkin tags: readonly-wal-recovery
17:29
Corrections to the Win32 porting changes on this branch. check-in: 0b26a5a2 user: mistachkin tags: readonly-wal-recovery
17:29
Make it possible to use OSTRACE for multi-process testing. check-in: 0a7d416c user: mistachkin tags: readonly-wal-recovery
16:30
Initial work on porting the changes on this branch to Win32. check-in: 3738bfd0 user: mistachkin tags: readonly-wal-recovery
2017-11-08
19:26
Extra comments on the sqlite3OsShmMap() call in walBeginUnlocked(). No changes to code. check-in: 033ee92b user: drh tags: readonly-wal-recovery
17:51
Turns out that SQLITE_READONLY_CANTLOCK is an historical name that must be preserved. So make a new SQLITE_READLOCK_CANTINIT name instead. check-in: 04974a8b user: drh tags: readonly-wal-recovery
17:32
Change the name of SQLITE_READONLY_CANTLOCK to SQLITE_READONLY_CANTINIT. check-in: 6d7f94fa user: drh tags: readonly-wal-recovery
2017-11-07
21:25
Update an assert in wal.c. check-in: 94527b89 user: dan tags: readonly-wal-recovery
21:15
Handle the race condition that may occur if another process connects and then checkpoints and truncates the wal file while a readonly-shm client is building its heap-memory wal-index. check-in: 5a6703fc user: dan tags: readonly-wal-recovery
15:43
On unix, if the *-shm file cannot be opened for read/write access, open it read-only and proceed as if the readonly_shm=1 URI option were specified. check-in: ba718754 user: dan tags: readonly-wal-recovery
09:08
Add fault-injection tests for the code on this branch. check-in: a7d949fb user: dan tags: readonly-wal-recovery
2017-11-06
19:49
Add further test cases for the new code on this branch. And a couple of fixes. check-in: 71af9acb user: dan tags: readonly-wal-recovery
2017-11-04
21:06
Add further tests for the code added on this branch. check-in: a6716fcd user: dan tags: readonly-wal-recovery
18:10
In cases where a readonly_shm client cannot take the DMS lock on the *-shm file, have it parse the wal file and create a wal-index to access it in heap memory. check-in: 18b26843 user: dan tags: readonly-wal-recovery
2017-11-02
18:57
Fix test cases in wal2.test broken by the locking change in the previous commit. check-in: f569c351 user: dan tags: readonly-wal-recovery
11:12
Avoid locking shm-lock WAL_READ_LOCK(0) during recovery. Doing this allows recovery to proceed while a readonly_shm connection in unlocked mode has an ongoing read transaction. check-in: 5190d84a user: dan tags: readonly-wal-recovery
2017-11-01
20:59
If a readonly_shm connection cannot map the *-shm file because no other process is holding the DMS lock, have it read from the database file only, ignoring any content in the wal file. check-in: ce5d13c2 user: dan tags: readonly-wal-recovery
07:06
Merge latest trunk changes into this branch. check-in: 985bfc99 user: dan tags: readonly-wal-recovery
06:59
Fix a race condition in os_unix.c that might allow a client to use a *-shm file corrupted by a power failure if another client fails between locking the *-shm file and truncating it to zero bytes. check-in: d655bfab user: dan tags: readonly-wal-recovery
2017-10-26
17:34
Fix an error in the previous commit on this branch. check-in: f71dfee0 user: dan tags: readonly-wal-recovery
17:05
Instead of extra locks, use F_GETLK to ensure that readonly_shm clients cannot connect to a wal-mode database if there are no writers. check-in: 5492f457 user: dan tags: readonly-wal-recovery
2017-10-25
23:28
Use extra locks to prevent a readonly_shm=1 process from connecting to a WAL-mode database if there are no writers. check-in: 35d97908 user: drh tags: readonly-wal-recovery