From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Cc: | Marcin Stępnicki <mstepnicki(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: one column from huge view |
Date: | 2007-07-12 12:51:36 |
Message-ID: | 20070712125136.GA37198@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Jul 12, 2007 at 09:50:42AM +0100, Heikki Linnakangas wrote:
> Marcin Stępnicki wrote:
> >Let's say I've got a view with 100 columns and 1mln rows; some of them are
> >calculated "on the fly". For some reason I want only one column from
> >this view:
> >
> >select col1 from huge_view;
> >
> >Now, does PostgreSQL skip all the calculations from other columns and
> >executes this query faster then select * from huge_view?
>
> In simple cases, yes. But for example, if you have a LEFT OUTER JOIN in
> the view, the join is performed even if your query doesn't return any
> columns from the outer relation. Also, if the calculation contains
> immutable functions, it's not skipped.
Don't you mean "if the calculation contains VOLATILE functions,
it's not skipped"?
--
Michael Fuhr
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-07-12 12:55:43 | Re: one column from huge view |
Previous Message | smiley2211 | 2007-07-12 12:39:40 | Re: TIMING A QUERY ??? |