Opened 5 years ago

Closed 5 years ago

#4344 closed enhancement (fixed)

Macro-based COSTS for version specific costing

Reported by: pramsey Owned by: pramsey
Priority: high Milestone: PostGIS 3.0.0
Component: postgis Version: master
Keywords: Cc:

Description

Because we cannot fully cost functions until Pg12/PostGIS 3, we need to macro-ize all costing, and then set higher costs on the new version case.

Change History (1)

comment:1 by pramsey, 5 years ago

Resolution: fixed
Status: newclosed

In 17307:

Add costs to functions in the form of macros:
_COST_LOW, _COST_MEDIUM, _COST_HIGH
Macros are set in sqldefines.h.in and are switched
on PgSQL version. Prior to PG12, costs should be
small or nonexistent, to avoid SQL inlining issues.
After Pg12, costs can be higher to hopefully
force more parallelism in plans.
Closes #4344

Note: See TracTickets for help on using tickets.