---
title: "PostgreSQL TimescaleDB Settings"
sidebar_label: "Settings"
sidebar_position: 4
description: "How to change PostgreSQL TimescaleDB settings"
---

import Formbricks from '@theme/MDXComponents/Formbricks'
import Settings from '@site/i18n/en/docusaurus-plugin-content-docs/current/_partials/managed-databases/postgresql/settings.mdx'
import HugePagesSetting from '@site/i18n/en/docusaurus-plugin-content-docs/current/_partials/managed-databases/postgresql/huge-pages-setting.mdx'

# PostgreSQL TimescaleDB Settings

<Settings DatabaseName="PostgreSQL TimescaleDB" slug="timescaledb" />

### List of settings that require a restart \{#list-of-settings-that-require-reboot}

* `autovacuum_freeze_max_age;`
* `autovacuum_max_workers;`
* `autovacuum_multixact_freeze_max_age;`
* `huge_pages;`
* `max_connections;`
* `max_files_per_process;`
* `max_locks_per_transaction;`
* `max_logical_replication_workers;`
* `max_pred_locks_per_transaction;`
* `max_prepared_transactions;`
* `max_wal_senders;`
* `max_worker_processes;`
* `old_snapshot_threshold;`
* `pg_stat_statements.max;`
* `shared_buffers;`
* `timescaledb.max_background_workers;`
* `track_activity_query_size.`

## Automatic settings adjustment during cluster scaling \{#automatically-changed-settings-after-scaling-up-cluster}

DBMS settings have valid value ranges. If, during [cluster scaling](/managed-databases/timescaledb/resize-cluster.mdx), setting values exceed the valid ranges, they are automatically replaced with default values so that the cluster can operate.

Once the cluster is scaled and enters the `ACTIVE` status, you can [change the settings](#change-settings) and set new values.

List of settings whose values are reverted to default when scaling the cluster:

* `autovacuum_max_workers;`
* `effective_cache_size;`
* `maintenance_work_mem;`
* `max_parallel_workers;`
* `max_wal_size;`
* `max_worker_processes;`
* `shared_buffers;`
* `vacuum_cost_limit;`
* `work_mem.`

<HugePagesSetting DatabaseName="PostgreSQL TimescaleDB" slug="timescaledb" />

<Formbricks />