Tiger Postgres configuration and tuning

Just as you can tune settings in Postgres, Tiger Postgres provides a number of configuration settings that may be useful to your specific installation and performance needs.

Just as you can tune settings in Postgres, 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 Postgres.

If enabled, aggregations are converted into partial aggregations during query planning. The first part of the aggregation is executed on a per-chunk basis. 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.

Enables or disables the vectorized optimizations in the query executor. For example, the sum() aggregation function on compressed chunks can be optimized in this way.

Set to ON to dramatically decrease the amount of data written on a continuous aggregate in the presence of a small number of changes, reduce the i/o cost of refreshing a continuous aggregate, and generate fewer Write-Ahead Logs (WAL). Only works for continuous aggregates that don't have compression enabled.

Max background worker processes allocated to TimescaleDB. Set to at least 1 + the number of databases loaded with the TimescaleDB extension in a Postgres instance. Default value is 16.

The default value for hypercore_use_access_method for functions that have this parameter. This function is in user context, meaning that any user can set it for the session. The default value is false.

Disable the loading of the actual extension

Enable group by reordering

Enable chunk append node

Enable constraint-aware append scans

Enable constraint exclusion

Enable job execution logging

Enable TimescaleDB query optimizations

Enable ordered append scans

Enable parallel chunk append node

Enable runtime chunk exclusion

Enable tiered reads to query your data normally when it's distributed across different storage tiers. Your hypertable is spread across the tiers, so queries and JOINs work and fetch the same data as usual.

By default, tiered data is not accessed by queries. Querying tiered data may slow down query performance as the data is not stored locally on Timescale's high-performance storage tier.

Enable transparent decompression

Stop any background workers which could have been performing tasks. This is especially useful if you migrate data to your Tiger Cloud service or self-hosted TimescaleDB.

Maximum cached chunks

Maximum open chunks per insert

The max number of tuples that can be decompressed during an INSERT, UPDATE, or DELETE.

Set TimescaleDB in restoring mode. It is disabled by default.

Change access to features based on the TimescaleDB license in use. For example, setting timescaledb.license to apache limits TimescaleDB to features that are implemented under the Apache 2 license. The default value is timescale, which allows access to all features.

Telemetry settings level. Level used to determine which telemetry to send. Can be set to off or basic. Defaults to basic.

Records last time timescaledb-tune ran.

Version of timescaledb-tune used to tune when it runs.