Skip to content

docs(duckdb): fix stale memory-limit guidance in 2.1.x accelerator guide #1936

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lukekim merged 1 commit into from
Jul 17, 2026
+2 −2
Merged

docs(duckdb): fix stale memory-limit guidance in 2.1.x accelerator guide #1936

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .../versioned_docs/version-2.1.x/components/data-accelerators/duckdb/deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ Datasets sharing a DuckDB instance share the pool. For write-heavy refresh plus

### Memory

DuckDB self-tunes its memory limit based on system memory. For containers, set a `memory_limit` pragma via the connection string to prevent OOM due to cgroup misdetection. Plan for the DuckDB working set plus ~2× for query execution headroom.
DuckDB self-tunes its memory limit based on system memory. For containers, set the `duckdb_memory_limit` acceleration parameter to prevent OOM due to cgroup misdetection. Plan for the DuckDB working set plus ~2× for query execution headroom.

### Index Parameters

Expand Down Expand Up @@ -92,7 +92,7 @@ DuckDB acceleration operations participate in [task history](../../../reference/
| Symptom | Likely cause | Resolution |
| ------------------------------------------------------ | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Slow first startup after restart | WAL replay due to ungraceful shutdown. | Use graceful shutdown (`SIGTERM`). Subsequent starts will be fast once the checkpoint is clean. |
| OOM on refresh | DuckDB memory limit too high for container cgroup. | Set a `memory_limit` pragma via the connection string. |
| OOM on refresh | DuckDB memory limit too high for container cgroup. | Set the `duckdb_memory_limit` acceleration parameter. |
| Disk fills during large queries | Spill directory on undersized volume. | Point `runtime.query.temp_directory` at a larger volume; monitor free space. |
| Query uses table scan when an index exists | `duckdb_index_scan_percentage` / `duckdb_index_scan_max_count` too low. | Tune thresholds; `EXPLAIN` to confirm. |
| Indexes disappear after refresh | `on_refresh_sort_columns` triggers `CREATE OR REPLACE`. | Re-create indexes post-refresh, or avoid sort-column refreshes until the underlying behavior is updated. |
Expand Down
Loading