Tom Lane <t...@sss.pgh.pa.us> wrote: > It's going to be a really, really, *really* hard sell to get us to > export any sort of external API to the parser internals. At least > if by "API" you mean something other than "we will whack this around > to an indefinite degree on no notice, and don't even think about > complaining". > > What exactly is the goal that you think such a thing would serve, > anyway? The fragments on the referenced web page don't leave me with > any warm feelings about how well the idea has been thought through.
Some of items in the referenced web page are just voted results form cluster projects. At this time, we should read them as "what is needed", but not "how to do it". They have been not reviewd yet and not well-considered to be official TODO items. I知 not sure what pgpool team think about, but I do NOT intend to export the existing internal functions as-is. As for my personal goal, I think pgpool should be re-implemented on the layers of SQL/MED FDW or planner/executor hooks. I'd say the SQL/MED FDW apporach is "one by one into core (from projects)", and the hook apporach is "external API (from core)". Regards, --- Takahiro Itagaki NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
