TimescaleDB configuration and tuning
Just as you can tune settings in PostgreSQL, TimescaleDB provides a number of configuration
settings that may be useful to your specific installation and performance needs. These can
also be set within the
postgresql.conf file or as command-line parameters
when starting PostgreSQL.
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 16.
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.
If enabled, TimescaleDB combines different chunks belonging to the same hypertable into a single query per data node. It is by default enabled.
When acting as a access node, TimescaleDB splits batches of inserted
tuples across multiple data nodes. It batches up to
max_insert_batch_size tuples per data node before flushing. Setting
this to 0 disables batching, reverting to tuple-by-tuple inserts. The
default value is 1000.
Enables binary format for data exchanged between nodes in the cluster. It is by default enabled.
Enables DDL operations on data nodes by a client and do not restrict execution of DDL operations only by access node. It is by default disabled.
Enables optimization that runs remote queries asynchronously across data nodes. It is by default enabled.
Enable getting and showing
EXPLAIN output from remote nodes. This
requires sending the query to the data node, so it can be affected
by the network connection and availability of data nodes. It is by default disabled.
Pick data fetcher type based on type of queries you plan to run, which
can be either
cursor. The default is
Specifies the path used to search user certificates and keys when
connecting to data nodes using certificate authentication. Defaults to
timescaledb/certs under the PostgreSQL data directory.
timescaledb.passfile (string) [
Specifies the name of the file where passwords are stored and when connecting to data nodes using password authentication.
Set TimescaleDB in restoring mode. It is by default disabled.
Change access to features based on the Timescale license in use. For example,
apache limits TimescaleDB to features that
are implemented under the Apache 2 license. The default value is
which allows access to all features.
Telemetry settings level. Level used to determine which telemetry to
send. Can be set to
basic. Defaults to
Records last time
timescaledb-tune used to tune when it ran.
Found an issue on this page?Report an issue!