From: | Nathan Bell <nathanb(at)actarg(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: 8.1 vs 8.2.1 view optimization |
Date: | 2007-01-16 21:55:08 |
Message-ID: | 45AD49BC.3030208@actarg.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(at)actarg(dot)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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-16 22:01:08 | Re: 8.1 vs 8.2.1 view optimization |
Previous Message | Jorge Godoy | 2007-01-16 21:47:28 | [1/2 OFF] Varlena.com inaccessible from .br (Blocked?) |