Thread: planner, how difficult to ...
I have been working with Postgres for just a short while, however, we are looking to use Postgres for our next project and I was hoping someone could answer a question for me regarding the planner to save me some research time.
How integrated is the planner into the database? Put another way, how hard would it be to separate the planner from the core database in such a way that it could be easily replaced either during compilation or even better with a runtime setting?
This could possibly led to a much easier way to work on and compare separate planners within Postgres without having to fork the code base.
Any opinions, answers, rants...
Thanks,
Keith
Keith Bottner wrote: > How integrated is the planner into the database? Put another way, how > hard would it be to separate the planner from the core database in > such a way that it could be easily replaced either during compilation > or even better with a runtime setting? The planner is configurable at run time in many ways. But maybe you want to start by explaining your problem instead of presuming a solution.
Peter Eisentraut wrote:
>Keith Bottner wrote:
>
>
>>How integrated is the planner into the database? Put another way, how
>>hard would it be to separate the planner from the core database in
>>such a way that it could be easily replaced either during compilation
>>or even better with a runtime setting?
>>
>>
>
>The planner is configurable at run time in many ways. But maybe you
>want to start by explaining your problem instead of presuming a
>solution.
>
>
you can already "change" the planner.
just use GEQO instead of exhaustive searching,
why would you want to change the existing planner?
implementing a rule based planner like the one Oracle had is not a good
idea ;).
regards,
Hans