Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Marcin StÄpnicki wrote:
>> Now, does PostgreSQL skip all the calculations from other columns and
>> executes this query faster then select * from huge_view?
> In simple cases, yes.
A rule of thumb is that it's been optimized if you don't see a "Su
Michael Fuhr wrote:
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;
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;
> >
>
Marcin Stępnicki wrote:
Hello.
I've googled a bit but I think I can't match the keywords, so I thought
I'll ask here:
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
Hello.
I've googled a bit but I think I can't match the keywords, so I thought
I'll ask here:
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 PostgreS
