pgsql: Move checking an explicit VARIADIC "any" argument into the parse

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Move checking an explicit VARIADIC "any" argument into the parse
Date: 2013-07-18 16:00:33
Message-ID: E1Uzqd7-0002jg-TK@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Move checking an explicit VARIADIC "any" argument into the parser.

This is more efficient and simpler . It does mean that an untyped NULL
can no longer be used in such cases, which should be mentioned in
Release Notes, but doesn't seem a terrible loss. The workaround is to
cast the NULL to some array type.

Pavel Stehule, reviewed by Jeevan Chalke.

Branch
------
master

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

Modified Files
--------------
src/backend/catalog/pg_aggregate.c | 4 +++-
src/backend/parser/parse_func.c | 22 ++++++++++++++++++-
src/backend/utils/adt/ruleutils.c | 4 +++-
src/backend/utils/adt/varlena.c | 42 ++++++++++++++----------------------
src/include/parser/parse_func.h | 4 ++--
src/test/regress/expected/text.out | 10 +++++----
src/test/regress/sql/text.sql | 8 +++----
7 files changed, 55 insertions(+), 39 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2013-07-18 18:55:43 pgsql: Fix pgstattuple functions to use regclass-type as the argument.
Previous Message Tom Lane 2013-07-18 05:02:33 pgsql: Fix direct access to Relation->rd_indpred.