Hi,
In the partition_aggregate tests, there's a case where the explained
query doesn't match the query that's executed just below. This has
existed since the file was first committed (e2f1eb0ee3), and doesn't
materially affect the plan, but if any issues were introduced it might
not show up in this part of the test, so we should probably fix it.
Attached is a simple fix. I noticed the issue whilst debugging my
low-rowcount parallel scan costing efforts [0].
Kind regards,
Matthias van de Meent
Databricks (https://www.databricks.com)
[0] https://postgr.es/m/CAEze2Wi+Jp26mhBJvrMshKGYNTtPcxzd1BWoEW_7+eH6saj3gQ@mail.gmail.com
