Re: STABLE functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joachim Wieland <jwieland(at)kawo2(dot)rwth-aachen(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: STABLE functions
Date: 2003-04-25 15:13:06
Message-ID: 20595.1051283586@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joachim Wieland <jwieland(at)kawo2(dot)rwth-aachen(dot)de> writes:
> So why is a
> SELECT ... FROM table WHERE col = f(...)
> (with a STABLE function f) not a "single table scan"

The point is that the system *may* choose to evaluate f() only once,
not that it *must* do so. The classification exists to make it valid
to use an indexscan on "col".

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message pgsql 2003-04-25 15:33:36 Re: close() vs. closesocket()
Previous Message Joachim Wieland 2003-04-25 14:50:08 Re: STABLE functions