Robert Haas <robertmh...@gmail.com> writes: > Hi, > > ... As a recap, my overall goal here > is to make it so that you can examine a finished plan, figure out what > decisions the planner made, and then somehow get the planner to make > those same decisions over again in a future planning cycle.
I am feeling that this is similar with Oracle's outline feature, where the final plan is examined and then a series of hints are stored and then during the replanning of the the same query, these hints will be applied to planner. If one of the hints is not appliable any more, like the index is unusable, it is just ignored. > This list of elided nodes is stored in the PlannedStmt I did a quick check on the attached patches and I can see some more information is added into PlannedStmt. then my question are the PlannedStmt is not avaiable during the future planning cycle, then how does these information would be helpful on the feture planning? and I'm strange that there are little changes on the optimizer part. Does this patchset just a preparation work for reconstructing a same plan in future? > outside of the portion of the tree that actually gets executed, so > that code that is doing plan tree inspection can look at it but > execution doesn't get any slower. Thank you for sharing this! -- Best Regards Andy Fan
