pgsql: Ensure generic plan gets used for a plpgsql expression with no p - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Ensure generic plan gets used for a plpgsql expression with no p
Date
Msg-id E1R4bKQ-00024F-Ps@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Ensure generic plan gets used for a plpgsql expression with no parameters.

Now that a NULL ParamListInfo pointer causes significantly different
behavior in plancache.c, be sure to pass it that way when the expression
is known not to reference any plpgsql variables.  Saves a few setup
cycles anyway.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/e6ed34f70d57d102da8383919e0046c577d317e7

Modified Files
--------------
src/pl/plpgsql/src/pl_exec.c |   27 ++++++++++++++++++++-------
1 files changed, 20 insertions(+), 7 deletions(-)


pgsql-committers by date:

Previous
From: itagaki@pgfoundry.org (User Itagaki)
Date:
Subject: textsearch-ja - textsearch-ja: Support EXTENSION for PostgreSQL 9.1.
Next
From: Tom Lane
Date:
Subject: pgsql: Avoid unnecessary page-level SSI lock check in heap_insert().