qsliu

> @qsliu2017 [4paradigm/OpenMLDB/actions/runs/3102510202/jobs/5024874140#step:9:43](https://github.com/4paradigm/OpenMLDB/actions/runs/3102510202/jobs/5024874140#step:9:43) tests failed ? addressed

@caarlos0 Could you explain why #3073 fail? thanks.

updated. @caarlos0 please take a look

I'd like to have a try

> @qsliu2017 What databases are you diffing? We recently fixed this for postgres: #812 oracle :(

I encounter the same performance decrease issue on MySQL. TPC-H(sf=1) Query 17 in PG+DuckDB costs 2.15s while MySQL costs 30.37s! And `filter_pushdown` does not help. I sample both scenarios and...

I also set debug_show_queries to both and find that mysql scanner does not implement the [parallel scan](https://duckdb.org/2022/09/30/postgres-scanner#parallelization) used in postgres

hey @Tishj, I just add some cases of quoted column but they failed, though It's okay in CLI. Seems like `PRAGMA enable_verification` is the cause. Any suggestion?

Found it! `parsed_statement_verifier` transforms the already parsed `SQLStatement` to string then parses it again. https://github.com/duckdb/duckdb/blob/86f853d9eeae0b07cb2397f2380d2cbf81d2fbc6/src/verification/parsed_statement_verifier.cpp#L11-L15 The quotes lost since the `EXCLUDE` columns are stored in string (so are the `REPLACE`...

> I'm not entirely sure I understand the issue from your description though Currently the exclude columns are stored in `case_insensitive_set_t`, i.e. `unordered_set`, without quotes. https://github.com/duckdb/duckdb/blob/86f853d9eeae0b07cb2397f2380d2cbf81d2fbc6/src/include/duckdb/parser/expression/star_expression.hpp#L26-L29 However, aforementioned `parsed_statement_verifier` calls...