Re: [PERFORM] View vs Stored Proc Performance

2009-09-12 Thread Dimitri Fontaine
Merlin Moncure  writes:
> like joining the result to another table...the planner can see
> 'through' the view, etc.  in a function, the result is fetched first
> and materialized without looking at the rest of the query. 

I though the planner would "see through" SQL language functions and
inline them when possible, so they often can make for parametrized
views...

Regards,
-- 
dim

-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance


Re: [PERFORM] View vs Stored Proc Performance

2009-09-12 Thread Merlin Moncure
On Sat, Sep 12, 2009 at 7:51 AM, Dimitri Fontaine
 wrote:
> Merlin Moncure  writes:
>> like joining the result to another table...the planner can see
>> 'through' the view, etc.  in a function, the result is fetched first
>> and materialized without looking at the rest of the query.
>
> I though the planner would "see through" SQL language functions and
> inline them when possible, so they often can make for parametrized
> views...

It can happen for simple functions but often it will not.  For views
it always happens.

merlin

-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance