From ef48ed4c86e65c9a173ead5e08ec23f783849b51 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 22 Nov 2007 19:40:25 +0000 Subject: 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. --- src/include/nodes/primnodes.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/include/nodes/primnodes.h') diff --git a/src/include/nodes/primnodes.h b/src/include/nodes/primnodes.h index 4b940791a28..bc8064ece49 100644 --- a/src/include/nodes/primnodes.h +++ b/src/include/nodes/primnodes.h @@ -10,7 +10,7 @@ * Portions Copyright (c) 1996-2007, PostgreSQL Global Development Group * Portions Copyright (c) 1994, Regents of the University of California * - * $PostgreSQL: pgsql/src/include/nodes/primnodes.h,v 1.135 2007/11/15 22:25:17 momjian Exp $ + * $PostgreSQL: pgsql/src/include/nodes/primnodes.h,v 1.136 2007/11/22 19:40:25 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -302,7 +302,7 @@ typedef struct FuncExpr * * Note that opfuncid is not necessarily filled in immediately on creation * of the node. The planner makes sure it is valid before passing the node - * tree to the executor, but during parsing/planning opfuncid is typically 0. + * tree to the executor, but during parsing/planning opfuncid can be 0. */ typedef struct OpExpr { -- cgit v1.2.3