Skip to content
ClickHouse Docs
ClickHouse DocsClickHouse Docs
49.6kGet Started

use_partition_* session settings

View as MarkdownEdit this pageReport an issueSet up docs MCP

These settings are available in system.settings and are autogenerated from source.

use_partition_minmax_for_primary_key_pruning

Type
Bool
Default
1
Version history
VersionDefault valueComment
26.71New setting to use the part's partition minmax to prune more granules during primary key analysis for `MergeTree` tables, when a primary key column is also an input column of the partition key.

Use partition minmax index bounds to prune more granules during primary key analysis for MergeTree tables, when a primary key column is also an input column of the partition key.

For example, in a MergeTree table with ORDER BY (id, event_time) and PARTITION BY toYYYYMM(event_time), ClickHouse will use the partition minmax index on event_time during primary key index analysis to make more informed granule-pruning decisions.

Possible values:

  • 0 — Disabled.
  • 1 — Enabled.

use_partition_pruning

Aliases: use_partition_key

Type
Bool
Default
1
Version history
VersionDefault valueComment
26.31New setting controlling whether MergeTree uses partition key for pruning. 'use_partition_key' is an alias for this setting.

Use partition key to prune partitions during query execution for MergeTree tables.

Possible values:

  • 0 — Disabled.
  • 1 — Enabled.
Navigation