summaryrefslogtreecommitdiffstats
path: root/www/wal.html
diff options
context:
space:
mode:
Diffstat (limited to 'www/wal.html')
-rw-r--r--www/wal.html14
1 files changed, 5 insertions, 9 deletions
diff --git a/www/wal.html b/www/wal.html
index 2e32dba..ed46f5c 100644
--- a/www/wal.html
+++ b/www/wal.html
@@ -187,14 +187,10 @@ a rollback journal. Advantages include:</p>
<p>But there are also disadvantages:</p>
<ol>
-<li>WAL normally requires that the <a href="vfs.html">VFS</a>
- support shared-memory primitives.
- (Exception: <a href="wal.html#noshm">WAL without shared memory</a>)
- The built-in unix and windows VFSes
- support this but third-party extension VFSes for custom operating
- systems might not.
-</li><li>All processes using a database must be on the same host computer;
- WAL does not work over a network filesystem.
+<li>All processes using a database must be on the same host computer;
+ WAL does not work over a network filesystem. This is because WAL requires
+ all processes to share a small amount of memory and processes on
+ separate host machines obviously cannot share memory with each other.
</li><li>Transactions that involve changes against multiple <a href="lang_attach.html">ATTACHed</a>
databases are atomic for each individual database, but are not
atomic across all databases as a set.
@@ -750,5 +746,5 @@ PRAGMA journal_mode=DELETE;
<p>Deliberately changing out of WAL mode changes the database file format
version numbers back to 1 so that older versions of SQLite can once again
access the database file.</p>
-<p align="center"><small><i>This page last modified on <a href="https://sqlite.org/docsrc/honeypot" id="mtimelink" data-href="https://sqlite.org/docsrc/finfo/pages/wal.in?m=d53a5bd13a">2024-02-13 18:06:21</a> UTC </small></i></p>
+<p align="center"><small><i>This page last modified on <a href="https://sqlite.org/docsrc/honeypot" id="mtimelink" data-href="https://sqlite.org/docsrc/finfo/pages/wal.in?m=9082744b12">2024-07-14 23:07:20</a> UTC </small></i></p>