Hi all, Since current dynamic query memory control doesn't work well, and causes many problems, like memory can't be released, which may be caused by bugs, and memory is calculated incorrectly that some queries can't be executed even if then can actually. Therefore, we decided to remove it.
However, we still need a restriction to limit the max number of paths that users can query in case SQL like "select * from root" is executed, which leads to a OOM. So we can still keep the `max_deduplicated_path_num` parameter and just remove the dynamic calculation. We will try to implement a more stable version of query memory control later. If you are interested in this, welcome to discussion and contributions. Thanks. Regards -- Best, Xiangwei Wei
