**Describe the bug**

Since we upgraded to 20.10.3.30, one of our clickhouse cluster takes much more time to start. (Up to 50 minutes, and before it took ~3 minutes)
The log file is filled with
>  <Debug> DiskLocal: Reserving 1.00 MiB on disk `default`, having unreserved 16.90 TiB

Additionally, the memory consumption increases, linearly, a lot (up to arround 230 G for us) and then drop back to normal values once clickhouse finished starting up. During that loading phase, a single CPU core is used at 100%.
If that memory is not available for the machine, clickhouse gets OOMed by the kernel.


**How to reproduce**
* Issue appeared after we upgraded to ClickHouse server version 20.10.3.30

* How could I find wich of our tables may be responsible for that ?


**Expected behavior**
A fast startup :)

/
    /
    if (select_query->hasJoin())
        return std::nullopt;
    /
    if (select_query->interpolate() && !select_query->interpolate()->children.empty())
        return std::nullopt;
    /
    if (select_query->group_by_with_grouping_sets)
        return std::nullopt;
    auto query_options = SelectQueryOptions(
        QueryProcessingStage::WithMergeableState,
        / 1,
        / true
    ).ignoreProjections().ignoreAlias();
    InterpreterSelectQuery select(
        query_ptr,
        query_context,
        query_options,
        query_info.prepared_sets);
    const auto & analysis_result = select.getAnalysisResult();
    query_info.prepared_sets = select.getQueryAnalyzer()->getPreparedSets();
    query_info.prewhere_info = analysis_result.prewhere_info;
    const auto & before_where = analysis_result.before_where;
    const auto & where_column_name = analysis_result.where_column_name;
    /
    ActionDAGNodes added_filter_nodes;
    if (auto additional_filter_info = select.getAdditionalQueryInfo())
        added_filter_nodes.nodes.push_back(&additional_filter_info->actions->findInOutputs(additional_filter_info->column_name));
    if (before_where)