Skip to content

Document timescaledb.bgw_scheduler_restart_time (#2748) #2772

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.

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

Draft
wants to merge 6 commits into
base: latest
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
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
7 changes: 7 additions & 0 deletions self-hosted/configuration/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -195,6 +195,13 @@ Max background worker processes allocated to TimescaleDB. Set to at
least 1 + number of databases in Postgres instance to use background
workers. Default value is 8.

### `timescaledb.bgw_scheduler_restart_time (int)`

Scheduler restart time in seconds. If the scheduler encounters an
error, it exits with an error code and restarts after
`timescaledb.bgw_scheduler_restart_time` seconds. Default value is 30
seconds. You can set this to a value between 1 and 3600 seconds.

### Distributed hypertables

#### `timescaledb.hypertable_distributed_default (enum)`
Expand Down
11 changes: 9 additions & 2 deletions self-hosted/configuration/timescaledb-config.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,14 @@ Max background worker processes allocated to TimescaleDB. Set to at least 1 +
the number of databases loaded with a TimescaleDB extension in a PostgreSQL
instance. Default value is 16.


### `timescaledb.bgw_scheduler_restart_time (int)`

Scheduler restart time in seconds. If the scheduler encounters an
error, it exits with an error code and restarts after
`timescaledb.bgw_scheduler_restart_time` seconds. Default value is 30
seconds. You can set this to a value between 1 and 3600 seconds.

## Query Planning and Execution

### `timescaledb.enable_chunkwise_aggregation (bool)`
Expand All @@ -30,7 +38,6 @@ Then, these partial results are combined and finalized. Splitting aggregations
decreases the size of the created hash tables and increases data locality, which
speeds up queries.


### `timescaledb.vectorized_aggregation (bool)`
Enables or disables the vectorized optimizations in the query executor. For
example, the `sum()` aggregation function on compressed chunks can be optimized
Expand All @@ -44,7 +51,7 @@ Enables two-phase commit for distributed hypertables. If disabled, it
uses a one-phase commit instead, which is faster but can result in
inconsistent data. It is by default enabled.

### `timescaledb.enable_per_data_node_queries`
### `timescaledb.enable_per_data_node_queries (bool)`

If enabled, TimescaleDB combines different chunks belonging to the
same hypertable into a single query per data node. It is by default enabled.
Expand Down