"Gurjeet Singh" <[EMAIL PROTECTED]> writes: > On Sat, Oct 4, 2008 at 8:49 AM, Tom Lane <[EMAIL PROTECTED]> wrote: > >> "Gurjeet Singh" <[EMAIL PROTECTED]> writes: >> > Shouldn't PG make all efforts to not execute something when the result is >> > already known? >> >> Not if said effort would cost more than is saved, which would be by far >> the most likely result if we tried to cache all function results. >> > > Sorry Tom, I confused STABLE with IMMUTABLE; my bad.
No, this is equally untrue for immutable. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
