Hi, Tom,
Tom Lane wrote:
Neil Conway [EMAIL PROTECTED] writes:
BTW, I think it would make sense to implement a limited subset of the
xfunc ideas: add options to CREATE FUNCTION to allow cost information to
be specified, and then take advantage of this information instead of
using the
Markus Schaber [EMAIL PROTECTED] writes:
Tom Lane wrote:
The trick is to figure out what a useful parameterized cost model would
look like. IIRC, the main reason the xfunc code rotted on the vine was
that its cost parameters didn't seem to be either easy to select or
powerful in predicting
Neil Conway [EMAIL PROTECTED] writes:
BTW, I think it would make sense to implement a limited subset of the
xfunc ideas: add options to CREATE FUNCTION to allow cost information to
be specified, and then take advantage of this information instead of
using the existing constant kludges. This
On Mon, 2006-10-09 at 22:49 -0400, jungmin shin wrote:
Does anybody know what the Postgres does for optimizing the queries
with UDFs?
The optimizer considers function volatility to avoid reevaluating UDFs
needlessly, and to use index scans on predicates involving a function.
Also, functions
