Skip to content

Commit 00758d0

Browse files
claudespicelukekim
authored andcommitted
fix: Remove nonexistent turso_mvcc parameter from v1.11.x docs
The turso_mvcc parameter does not exist in the Spice codebase. MVCC is unconditionally enabled — PRAGMA journal_mode = 'mvcc' is set during every TursoConnectionPool::new_with_timestamp_format call. The vNext docs already correctly state that MVCC is automatically enabled. Changes: - Remove turso_mvcc from the configuration parameters list - Remove turso_mvcc: enabled from YAML examples - Update MVCC section to state MVCC is automatically enabled (matching vNext wording)
1 parent 481c2ae commit 00758d0

1 file changed

Lines changed: 2 additions & 11 deletions

File tree

  • website/versioned_docs/version-1.11.x/components/data-accelerators

website/versioned_docs/version-1.11.x/components/data-accelerators/turso.md

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,6 @@ datasets:
6060
Turso acceleration supports the following optional parameters under `acceleration.params`:
6161

6262
- `turso_file` (string, default: `.spice/data/{dataset_name}.turso`): Path to the Turso database file. Only applies if `mode` is `file`. If the file does not exist, Spice creates it automatically.
63-
- `turso_mvcc` (string, default: `disabled`): Enable Multi-Version Concurrency Control (MVCC) for improved concurrent read/write performance. Values: `enabled`, `disabled`.
6463
- `internal_timestamp_format` (string, default: `rfc3339`): Internal timestamp storage format. See [Timestamp Storage](#timestamp-storage) section. Values: `rfc3339`, `integer_millis`.
6564

6665
### Example Configuration
@@ -77,7 +76,6 @@ datasets:
7776
refresh_check_interval: 10m
7877
params:
7978
turso_file: ./orders.turso
80-
turso_mvcc: enabled
8179
```
8280

8381
Refer to the [datasets configuration reference](../../reference/spicepod/datasets#acceleration) for additional supported fields.
@@ -116,16 +114,9 @@ acceleration:
116114
117115
### MVCC Support
118116
119-
Multi-Version Concurrency Control (MVCC) can be enabled for improved concurrent read/write performance:
117+
Multi-Version Concurrency Control (MVCC) is automatically enabled for all Turso-accelerated datasets. The Turso accelerator sets `PRAGMA journal_mode = 'mvcc'` during connection pool initialization, enabling concurrent transactions via `BEGIN CONCURRENT`.
120118

121-
```yaml
122-
acceleration:
123-
engine: turso
124-
params:
125-
turso_mvcc: enabled
126-
```
127-
128-
When MVCC is enabled:
119+
When MVCC is active:
129120

130121
- Concurrent reads and writes perform better
131122
- Indexes are not yet supported (a warning is logged if indexes are configured)

0 commit comments

Comments
 (0)