> ## Documentation Index
> Fetch the complete documentation index at: https://clickhouse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# exclude_* MergeTree table settings

> ClickHouse MergeTree table settings in the exclude_* generated group.

export const SettingsInfoBlock = ({type, default_value, changeable_without_restart}) => {
  return <div className="not-prose" style={{
    display: "flex",
    flexWrap: "wrap",
    alignItems: "baseline",
    columnGap: "0.5rem",
    rowGap: "0.125rem",
    margin: "0.375rem 0",
    fontSize: "0.8125rem",
    lineHeight: "1.125rem"
  }}>
      <div style={{
    fontWeight: 600,
    opacity: 0.72
  }}>Type</div>
      <div style={{
    overflowWrap: "anywhere"
  }}>{type}</div>
      <div style={{
    fontWeight: 600,
    opacity: 0.72,
    marginInlineStart: "0.5rem"
  }}>Default</div>
      <div style={{
    overflowWrap: "anywhere"
  }}>{default_value}</div>
      {changeable_without_restart && <div style={{
    fontWeight: 600,
    opacity: 0.72,
    marginInlineStart: "0.5rem"
  }}>
          Changeable without restart
        </div>}
      {changeable_without_restart && <div style={{
    overflowWrap: "anywhere"
  }}>
          {changeable_without_restart}
        </div>}
    </div>;
};

These settings are available in [system.merge\_tree\_settings](/docs/reference/system-tables/merge_tree_settings) and are autogenerated from ClickHouse source.

<h2 id="exclude_deleted_rows_for_part_size_in_merge">
  exclude\_deleted\_rows\_for\_part\_size\_in\_merge
</h2>

<SettingsInfoBlock type="Bool" default_value="0" />

If enabled, estimated actual size of data parts (i.e., excluding those rows
that have been deleted through `DELETE FROM`) will be used when selecting
parts to merge. Note that this behavior is only triggered for data parts
affected by `DELETE FROM` executed after this setting is enabled.

Possible values:

* `true`
* `false`

**See Also**

* [load\_existing\_rows\_count\_for\_old\_parts](/docs/reference/settings/merge-tree-settings/other#load_existing_rows_count_for_old_parts)
  setting

<h2 id="exclude_materialize_skip_indexes_on_merge">
  exclude\_materialize\_skip\_indexes\_on\_merge
</h2>

<VersionHistory rows={[{"id": "row-1","items": [{"label": "25.10"},{"label": ""},{"label": "New setting."}]}]} />

Excludes provided comma delimited list of skip indexes from being built and stored during merges. Has no effect if
[materialize\_skip\_indexes\_on\_merge](/docs/reference/settings/merge-tree-settings/materialize#materialize_skip_indexes_on_merge) is false.

The excluded skip indexes will still be built and stored by an explicit
[MATERIALIZE INDEX](/docs/reference/statements/alter/skipping-index#materialize-index) query or during INSERTs depending on
the [materialize\_skip\_indexes\_on\_insert](/docs/reference/settings/session-settings#materialize_skip_indexes_on_insert)
session setting.

Example:

```sql theme={null}
CREATE TABLE tab
(
a UInt64,
b UInt64,
INDEX idx_a a TYPE minmax,
INDEX idx_b b TYPE set(3)
)
ENGINE = MergeTree ORDER BY tuple() SETTINGS exclude_materialize_skip_indexes_on_merge = 'idx_a';

INSERT INTO tab SELECT number, number / 50 FROM numbers(100); -- setting has no effect on INSERTs

-- idx_a will be excluded from update during background or explicit merge via OPTIMIZE TABLE FINAL

-- can exclude multiple indexes by providing a list
ALTER TABLE tab MODIFY SETTING exclude_materialize_skip_indexes_on_merge = 'idx_a, idx_b';

-- default setting, no indexes excluded from being updated during merge
ALTER TABLE tab MODIFY SETTING exclude_materialize_skip_indexes_on_merge = '';
```