For some reasons when we delete a MergeTree Part in atomic way something may go wrong - and leave the `delete_tmp_*` folder or it's part on disk. This may lead to a disk space consumption over time.

It's suggested to delete this folders at least at server start-up. Current solution with `clearOldTemporaryDirectories()` doesn't work because this method is called periodically from a thread without any locks or advisory on folders - it may cause the race conditions.
}
                const String partition_id = part->storage.getPartitionIDFromQuery(command.partition, getContext());
                if (partition_id == part->info.partition_id)
                {
                    is_partition_affected = true;
                    break;
                }
            }
            if (!is_partition_affected)
            {
                
                
                auto block_range = std::make_pair(part->info.min_block, part->info.max_block);
                updated_version_by_block_range[block_range] = last_mutation_to_apply->first;
                were_some_mutations_for_some_parts_skipped = true;
                continue;
            }
            auto new_part_info = part->info;
            new_part_info.mutation = last_mutation_to_apply->first;
            future_part->parts.push_back(part);
            future_part->part_info = new_part_info;
            future_part->name = part->getNewName(new_part_info);
            future_part->type = part->getType();
            tagger = std::make_unique<CurrentlyMergingPartsTagger>(future_part, MergeTreeDataMergerMutator::estimateNeededDiskSpace({part}), *this, metadata_snapshot, true);
            return std::make_shared<MergeMutateSelectedEntry>(future_part, std::move(tagger), commands, txn);
        }
    }
    return {};
}
bool StorageMergeTree::scheduleDataProcessingJob(BackgroundJobsAssignee & assignee)