ClickHouse Materialized View auto-runs after restart causing OOM loop

### Company or project name

_No response_

### Question

ClickHouse Materialized View auto-runs after restart causing OOM loop

I’m running ClickHouse in Docker on a high-memory server (~380GB RAM) to process large datasets.

I use several Materialized Views (MV) for heavy aggregation / transformation.
The problem is:

During MV refresh / backfill, ClickHouse consumes a huge amount of RAM

This leads to OOM, and the ClickHouse Docker container restarts

After restart, Materialized Views automatically start consuming data again

This creates a restart loop due to repeated memory spikes

What I want

I’m looking for a way to:

Prevent Materialized Views from automatically running after ClickHouse restart

Keep MVs in a stopped / disabled state by default

Manually start or attach MVs later via script or at a controlled time

Question

Is there a built-in way in ClickHouse to disable / pause Materialized Views across restarts?

Or any recommended pattern (detach/attach, settings, startup scripts, etc.) to control when MVs start consuming data?

Thanks in advance for any help or best practices.