Re: Optimize expresiions.

From: "Adam Rich" <adam(dot)r(at)sbcglobal(dot)net>
To: <han(dot)holl(at)informationslogik(dot)nl>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Optimize expresiions.
Date: 2007-01-11 14:03:48
Message-ID: 044701c73589$50e7aae0$6400a8c0@dualcore
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


How about this?

select item, very_expensive_function(item) as exp, cheap
from ( Select item, cheap_function(item) as cheap
From atable where cheap_function(item) > 0 ) sub
where very_expensive_function(item) > 0

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of
han(dot)holl(at)informationslogik(dot)nl
Sent: Thursday, January 11, 2007 4:59 AM
To: pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] Optimize expresiions.

Hello,

Given a table:
create table atable (
item integer;
);
and a view:
create view aview as select
item,
very_expensive_function(item) as exp,
cheap_function(item) as cheap
from atable;

Now the query:
select item from aview where exp > 0 and cheap > 0;
will lead to a sequential scan on atable with filter:
very_expensive_function(item) > 0 and cheap_function(item) > 0

The query would run much faster with the filter reordered.
Is there a way to tell the planner/optimizer that certain functions are
more
expensive than others, and should be postponed in lazy evaluation ?
Or is there a hook in the system that would allow me too look at and
maybe
reorder expressions before they are executed ?

Cheers,

Han Holl

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-01-11 14:07:36 Re: TRIGGER BEFORE INSERT
Previous Message Martijn van Oosterhout 2007-01-11 13:48:06 Re: Knowing the length(convert(username using windows_1251_to_utf8))