Fix performance regression in split scheduling introduced in 0.191. If a query
scans a non-trivial number of splits (~1M splits in an hour), the coordinator
CPU utilization can be very high, leading to elevated communication failures.
Fix correctness issue in the geometry_to_bing_tiles() function that causes
it to return irrelevant tiles when bottom or right side of the bounding box of the
geometry is aligned with the tile border.
Fix handling of invalid WKT (well-known text) input in geospatial functions.
Fix an issue that can cause long-running queries to hang when writer scaling is enabled.
Fix cast from REAL or DOUBLE to DECIMAL to conform to the SQL standard.
For example, previously cast(double'100000000000000000000000000000000'asdecimal(38))
would return 100000000000000005366162204393472. Now it returns 100000000000000000000000000000000.
Fix bug in validation of resource groups that prevented use of the WEIGHTED_FAIR policy.
Fail queries properly when the coordinator fails to fetch data from workers.
Previously, it would return an HTTP 500 error to the client.
Improve memory tracking for queries involving DISTINCT or row_number() that could cause
over-committing memory resources for short time periods.
Improve performance for queries involving grouping().
Improve buffer utilization calculation for writer scaling.
Remove tracking of per-driver peak memory reservation.
Add resource-groups.max-refresh-interval config option to limit the maximum acceptable
staleness of resource group configuration.
Remove dictionary-processing-joins-enabled configuration option and dictionary_processing_join