pgsql: Actually ... - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Actually ...
Date
Msg-id 20071122194025.717767540F0@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Actually ... it's pretty silly that parse_oper.c doesn't set up the
opfuncid of an OpExpr initially, considering that it has the information
at hand already.  We'll still treat opfuncid as a cache rather than a
guaranteed-valid value, but this change saves one more syscache lookup
in the normal code path.

Modified Files:
--------------
    pgsql/src/backend/parser:
        parse_oper.c (r1.97 -> r1.98)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_oper.c?r1=1.97&r2=1.98)
    pgsql/src/include/nodes:
        primnodes.h (r1.135 -> r1.136)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/primnodes.h?r1=1.135&r2=1.136)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Save one syscache lookup when examining volatility or strictness
Next
From: jwp@pgfoundry.org (James William Pye)
Date:
Subject: python - lo: Correct Typo.