Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Tue, 16 May 2006 09:33:14 -0400
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
- Follow-Ups:
- Re: IMMUTABLE?
- From: Joachim Wieland
- Re: IMMUTABLE?
- References:
- IMMUTABLE?
- From: David Wheeler
- Re: IMMUTABLE?
- From: Tom Lane
- Re: IMMUTABLE?
- From: David Wheeler
- Re: IMMUTABLE?
- From: Tom Lane
- Re: IMMUTABLE?
- From: Joachim Wieland
- IMMUTABLE?
- Prev by Date: Re: Pgsql (and mysql) benchmark on T2000/Solaris and some
- Next by Date: Re: Pgsql (and mysql) benchmark on T2000/Solaris and some
- Previous by thread: Re: IMMUTABLE?
- Next by thread: Re: IMMUTABLE?
- Indexes: