Advanced parameters

It is possible to configure a wide variety of service database parameters by navigating to the Advanced parameters tab under the Database configuration heading. The advanced parameters are displayed in a scrollable and searchable list.

Expand image

As with the basic database configuration parameters, any changes are highlighted and the Apply changes, or Apply changes and restart, button is available, prompting you to confirm changes before the service is modified.

To create more than one database, you need to create a new service for each database. Timescale Cloud does not support multiple databases within the same service. Having a separate service for each database affords each database its own isolated resources.

You can also use schemas to organize tables into logical groups. A single database can contain multiple schemas, which in turn contain tables. The main difference between isolating with databases versus schemas is that a user can access objects in any of the schemas in the database they are connected to, so long as they have the corresponding privileges. Schemas can help isolate smaller use cases that do not warrant their own service.

Max background worker processes allocated to TimescaleDB. Set to at least 1 + the number of databases loaded with the TimescaleDB extension in a PostgreSQL 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 Timescale Cloud service or self-hosted database.

Maximum cached chunks

Maximum open chunks per insert

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