Josh Berkus <josh@agliodbs.com> writes:
> Still sounds good. Do you think that this system could be extended to other
> add-ons in the future which are currently more complex builds? And allow us
> to out some of the wierder things in /contrib?
The "system" already exists --- it's pgxs. We already have a report
from Thomas Hallgren that pgxs works for building pljava, so I'm not
too concerned about assuming it can be used for the other PLs. And
I think we have already pgxs-ified all of contrib, though that's
not the current standard method of building contrib.
I have no problem with pushing out any part of contrib that doesn't seem
tightly tied to the core server. I'm not entirely sure where to draw
the line, but for instance I'd probably want to keep dblink where it is,
since functions-returning-records are still in considerable flux.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
