Settings: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Settings are changed by: (settings "key" "value") The following settings are available: * <code>"Backtrace"</code>: <code>true</code> or <code>false</code> whether to print backtraces from Scheme. Using true decreases the performance by ~10% but gives you better debugging capabilities. * <code>"PartitionMaxDimensions"</code>: number from 0 to 10 how many partitioning dimensions are allowed at max. 0 means, don't partition shards for values (use it to workaround bugs),...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Settings are changed by: |
Settings are changed by: |
||
(settings "key" "value") |
(settings "key" "value") |
||
| + | And read by: |
||
| + | (settings "key") |
||
The following settings are available: |
The following settings are available: |
||
Revision as of 23:03, 17 May 2024
Settings are changed by:
(settings "key" "value")
And read by:
(settings "key")
The following settings are available:
"Backtrace":trueorfalsewhether to print backtraces from Scheme. Using true decreases the performance by ~10% but gives you better debugging capabilities."PartitionMaxDimensions": number from 0 to 10 how many partitioning dimensions are allowed at max. 0 means, don't partition shards for values (use it to workaround bugs), 1 means only one-dimensional partitioning."DefaultEngine": one of"memory" "sloppy" "logging" "safe"that defines which persistency level to choose if a CREATE TABLE statement is executed without theENGINEparameter