Yes, this turns out to be a volatile user-defined function. Is there some specific part of the
documentation you can point me to that helps explain why a volatile function might affect the plan
for a column not involved in select or join operations? I happened to pull this function off a
posting somewhere, so after reviewing the volatility keywords, volatile is clearly not required,
so that will be an easy fix. I'm still interested in knowing more about how volatility fits into
the query planner.
Thanks for your help.
-Brandon
--- Tom Lane wrote:
> What's isnumeric(), and is it by any chance marked volatile?
> If so, that's your problem.
>
> regards, tom lane
>
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
