Skip to content

docs: Durability section on txWalFlush (concurrency page) - #146

Merged
tae898 merged 1 commit into
mainfrom
docs/wal-flush-durability
Oct 29, 2026
Merged

tae898 merged 1 commit into
mainfrom
docs/wal-flush-durability

Conversation

@tae898

@tae898 tae898 commented Oct 29, 2026

Copy link
Copy Markdown
Collaborator

Adds a short "Durability: surviving power loss" section to how-to/concurrency.adoc, after "Signals and crashes", which already pointed to the main docs for WAL flush. It says that arcadedb.txWalFlush defaults to 0 (a commit survives a process crash, not power loss), shows how to set it to 1 from Python with ALTER DATABASE on both packages, how to set it process-wide with -D (jvm_args / ARCADEDB_JVM_ARGS for arcadedb-jvm, ARCADEDB_NATIVE_ISOLATE_ARGS for arcadedb), and links the main ArcadeDB docs for the semantics.

Verified on the native and JVM 26.11.1.dev0 wheels (Python 3.12, Linux): the default reads 0, the ALTER DATABASE makes it 1, a row commits, and the value is still 1 after a reopen. -D through jvm_args and through ARCADEDB_NATIVE_ISOLATE_ARGS also gave 1 on a new database. The order-of-magnitude commit cost (about 0.07 ms vs about 5 ms) is from one laptop and labelled as such.

🤖 Generated with Claude Code

Shows how to turn on WAL flushing from Python on both packages (SQL ALTER DATABASE, or -D through jvm_args / ARCADEDB_NATIVE_ISOLATE_ARGS), links the main docs for the semantics. Snippet run on the native and JVM 26.11.1.dev0 wheels.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@tae898
tae898 merged commit f53c0a1 into main Oct 29, 2026
1 check passed
@tae898
tae898 deleted the docs/wal-flush-durability branch October 29, 2026 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant