Eugene Klimov

@fzyzcjy sorry for late reply, is bug still relevant to you? Could you try to latest https://github.com/Altinity/clickhouse-backup/releases/tag/1.1.1? Which remote storage type do you use? Could you share your `config.yml` with...

your configuration looks OK. you can use forked repo if ready to adopt often path releases, or prefer original repo to more stable releases please report if OOM gone away

@fzyzcjy any news? Is OOM still present for your workload? Could you try the latest https://github.com/AlexAkulov/clickhouse-backup/releases/tag/v1.2.0?

@fzyzcjy is issue still relevant for you? could you try to use https://github.com/AlexAkulov/clickhouse-backup/releases/tag/v1.3.1

feature already implemented with `create --partitions=XXX,YYY` try latest 1.6.2

If I understood correctly, we already implement ```bash clickhouse-backup create --tables=*.table_name1,another_pattern ```

use case is not clear why you can't use --table parameter in your backup script? what is the difference from your side, between: ```bash clickhouse-backup -c config1.yml create clickhouse-backup -c...

i tried to plan to 2.0.0 (not released yer) @AngelLittleChaochao could you clear your use case? Why you can't use `table` parameter for POST /backup/actions or POST /backup/create API calls?...

Let's close issue because @vanyasvl doesn't provide more context

@michael-liumh Unfortunately, COS storage not tested enough, currently. Could you share debug logs? ``` LOG_LEVEL=debug ./clickhouse-backup download 1111111 -c config.yml ```