Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
The reasons are:
1) It is not used anymore.
2) Have seen crash due to this. The scenario is that:
The datalocality memory context on which resource_parameters is palloc-ed is reset before calculate_planner_segment_num() finishes, thus later access to resource_parameters could lead to crash or wrong results. A code path example which could lead to segfault is:
ProcessUtility()>PerformCursorOpen()>_copyPlannedStmt()->_copyQueryResourceParameters()
Attachments
Issue Links
- links to