On Wed, Jul 22, 2026 at 01:49:34AM +0300, Aleksander Alekseev wrote: >> I checked on the coverage that this patch effectively improves, but >> reviewing the report I notice that there's still some gap that can be >> fixed by just adding another nested path like this: >> >> NESTED PATH '$[*]' AS p1 COLUMNS (NESTED PATH '$[*]' AS p10 COLUMNS (a int)) >> NESTED PATH '$[*]' AS p2 COLUMNS (NESTED PATH '$[*]' AS p20 COLUMNS (b int)) > > Could you please clarify which lines of get_json_table_plan() this > will cover which are not currently covered by patch v2?
What are the old and new coverage numbers before and after the fact, and where are the zones impacted? I am seeing a mention to "improvements", but zero fact explaining things. This is mostly to get a feeling of the gain vs the runtime involved. -- Michael
signature.asc
Description: PGP signature
