Thanks to visit codestin.com
Credit goes to github.com

Skip to content

opt: update coster to account for cost of executing geospatial functions #48214

@rytaft

Description

@rytaft

As described in the Geospatial RFC, we will need to update the cost model of the optimizer to account for the fact that geospatial functions such as ST_Covers are expensive to execute. Currently, the cost model assumes that execution of scalar functions is basically free. We will need to change that assumption for geospatial functions.

Metadata

Metadata

Assignees

Labels

A-spatialSpatial work that is *not* related to builtins.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions