fdb-record-layer
fdb-record-layer copied to clipboard
introduce a planner budget
We need to limit the amount of work that is being done to plan a query. Two scenarios that come to mind:
- a bug somewhere in the planner leads to an unforeseen divergence which then causes infinite exploration
- infinite traversal of malformed tree or dag-like structures
- complex queries even in the absence of a bug may need an upper limit of the effort we put into planning them