Thread: pgsql: Save one syscache lookup when examining volatility or strictness

pgsql: Save one syscache lookup when examining volatility or strictness

From
tgl@postgresql.org (Tom Lane)
Date:
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)