Results of 1 - 2 of about 2 for autocheckpoint (0.002 sec.)
- Persistent Testing 11228
- By default, all tests are run in in-memory mode (unless --force-storage is enabled). In certain cases, we want to force the usage of a persistent database. We can initiate a persistent database using the load command, and trigger a reload o
...... restart query I SELECT * FROM test ORDER BY a ---- NULL 11 12 13 14 15 Note that by default the tests run with SET wal_autocheckpoint = '0KB' – meaning a checkpoint is triggered after every statement. WAL tests typically run with the following settings to...disable this behavior: statement ok PRAGMA disable_checkpoint_on_shutdown statement ok SET wal_autocheckpoint = '1TB'... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/persistent_testing.html
- Configuration 7485
- DuckDB has a number of configuration options that can be used to change the behavior of the system. The configuration options can be set using either the SET statement or the PRAGMA statement . They can be reset to their original values usi
...never checkpoints, DEFAULT defers to the global checkpoint_on_shutdown setting. VARCHAR DEFAULT checkpoint_threshold , wal_autocheckpoint The WAL size threshold at which to automatically trigger a checkpoint, e.g., 1GB. VARCHAR 16.0 MiB current_transaction_inv...IANT shredding enabled. Set to -1 to disable shredding entirely. Defaults to 1/4th of the row group size. BIGINT 30000 wal_autocheckpoint_entries Trigger automatic checkpoint when WAL entry count reaches or exceeds N (0 = disabled). UBIGINT 0 warnings_as_error... - https://man.mtool.work/duckdb/2.0/configuration/overview.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work