Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
7 check-ins using file src/os_unix.c version e376adf6
|
2017-11-07
| ||
| 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) | |