TennyZhuang

I've submitted a draft PR https://github.com/SchemaStore/schemastore/pull/2442 for partial support the feature. How can I test with taplo? I will finish the PR if I'm sure it can work well.

The PR is merged, so most fields are supported with the plugin except `workspace.dependencies`.

I guess we can close the issue as completed!

> We already have a similar one in IndexDeltaJoin PR, but it’s still under review. What's the difference between it and a trivial merger?

> LookupUnion is a new operator after merger. It will merge all items from each channel in order (first, second, third) instead of randomly pick one. > > To make...

Before it was implemented correctly, I think it's better to reject the query.

I don't think they are the high-priority tables. The key point is make psql's slash commands happy, so we can refer to [exec_command_d](https://github.com/postgres/postgres/blob/9a374b77fb53e4cfbca121e4fa278a7d71bde7c4/src/bin/psql/command.c#L713) At lease, some common used commands like...

I'd prefer to support the belows firstly: * \d * \dt tables * \di indexes * \dm materialized views

> updates come in batches of 1 or 2. How does it happen? Which executor produces the small chunk?

I can help to implement that.