Re: IMMUTABLE?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joachim Wieland <joe(at)mcknight(dot)de>
Cc: David Wheeler <david(at)kineticode(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: IMMUTABLE?
Date: 2006-05-16 13:33:14
Message-ID: 11508.1147786394@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Joachim Wieland <joe(at)mcknight(dot)de> writes:
> So irrespective of caching to prevent evaluation across statements, within a
> single statement, is there a strong reason why for example in
> WHERE col = f(const) with f() declared as immutable or stable and without an
> index on col, f() still gets called for every row? Or is this optimization
> just not done yet?

The above statement is not correct, at least not for immutable functions.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Arjen van der Meijden 2006-05-16 13:54:14 Re: Pgsql (and mysql) benchmark on T2000/Solaris and some
Previous Message Jignesh K. Shah 2006-05-16 13:19:47 Re: Pgsql (and mysql) benchmark on T2000/Solaris and some