pgsql: Save one syscache lookup when examining volatility or strictness

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Save one syscache lookup when examining volatility or strictness
Date: 2007-11-22 19:09:23
Message-ID: 20071122190923.29D7F7540F0@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Save one syscache lookup when examining volatility or strictness of
OpExpr and related nodes. We're going to have to set the opfuncid of
such nodes eventually (if we haven't already), so we might as well
exploit the opportunity to cache the function OID. Buys back some
of the extra planner overhead noted by Guillaume Smet, though I still
need to fool with equivclass.c to really respond to that.

Modified Files:
--------------
pgsql/src/backend/optimizer/util:
clauses.c (r1.251 -> r1.252)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c?r1=1.251&r2=1.252)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-11-22 19:40:25 pgsql: Actually ...
Previous Message Bruce Momjian 2007-11-22 17:51:39 pgsql: Add more comments about thousands separator handling.