Yeah, I saw the "not optimized out" typo as soon as I hit send.
What if the item that is taking a long time isn't a function, but rather
a sub-select?
Can I set the sub-select to stable, or perhaps set the entire view to
non-volatile to achieve the same result?
If not, can I set the sub-select to a different non-volatile view or do
I need to create a non-volatile function that returns the result?
Thanks for the help.
Tom Lane wrote:
>Nathan Bell <nathanb@actarg.com> writes:
>
>
>>Firing up 8.2.1 I notice that sub-items in a view are optimized out if
>>they aren't being selected.
>>
>>
>
>You mean "not optimized out", I suppose. Declare your function as
>non-volatile if you want the optimizer to assume it's OK to discard.
>
> regards, tom lane
>
>