Nirmit Shah

Much needed change, this would improve experience for contributors using Github Actions to debug test failures.

I would like to take up this issue, but can I know what is the expected output like what kind of formatted output are we looking for?

1.Should the Output Format Controlled via an Enum GUC? 2.Also we would need to bypass the JSON escape from PG Side Check https://github.com/postgres/postgres/blob/master/src/backend/commands/explain_format.c#L76

Does this plan output work ``` postgres=# explain (format json) SELECT * FROM duckdb.query($$ select '5874897-12-31'::date as date $$); QUERY PLAN -------------------------------------------------- [ + { + "Plan": { + "Node...

Just thinking out loud, for functions like read_parquet or other function returning rowsets , we should utilise `set_rel_pathlist_hook` with RTE kind as RTE_FUNCTION , and create a custom scan path...

@YuweiXiao , thanks for sharing your approach, It looks quiet interesting, while saying that I see we need to write a lot of code(type coercion/ tuple descriptor matching/ creating outer...

> Part 3 is probably impossible, because the postgres parser only considers the `*` as a single column. I think its possible , we would probably need a function that...

If you see the Redis Src Code all the 6 commands from #1250 - #1255 have common generic function [ref](https://github.com/redis/redis/blob/fdeb97629ef8964a5d9040328ee63734884ac874/src/geo.c#L523-L844) that is being used ideally one command should implement the...

> In my opinion, the generic function in Redis is pretty hard to read. It's more than 300 loc and has a lot of nested conditional clauses, especially when handling...

Can I take this up, if no one is working on it?