Skip to content

SYSTEM STOP MERGES not applying to newly created tables #91183

Open

Description

@benjaminwootton

Company or project name

No response

Describe the unexpected behaviour

If I run SYSTEM STOP MERGES then issue CREATE TABLE then the merge will still run for the newly created table

Not sure if by design or a bug but I think its more intuitive if stop merges prevents merges running for all objects including newly created

Which ClickHouse versions are affected?

25.10.2.65

How to reproduce

Clickhouse client

-- If I stop merges THEN create a table then merges still run for the table

SYSTEM STOP MERGES;
drop table foo;
create table foo( x UInt32 ) ENGINE=ReplacingMergeTree() ORDER BY x;
insert into foo values ( 123 );
insert into foo values ( 123 );
insert into foo values ( 123 );
-- Will merge

-- If I create a table THEN stop merges then merges do not run

drop table foo;
create table foo( x UInt32 ) ENGINE=ReplacingMergeTree() ORDER BY x;
SYSTEM STOP MERGES;
insert into foo values ( 123 );
insert into foo values ( 123 );
insert into foo values ( 123 );
-- Will not merge

Expected behavior

Merges stopped for all tables including newly created

Error message and/or stacktrace

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    comp-background-opsBackground pools/scheduling for merges, cleanup, maintenance.externalAuthor is not a member of the ClickHouse organizationunexpected behaviourResult is unexpected, but not entirely wrong at the same time.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions