pgsql: Support use of function argument names to identify which actual - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Support use of function argument names to identify which actual
Date
Msg-id 20091008023926.1BE85753FB7@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Support use of function argument names to identify which actual arguments
match which function parameters.  The syntax uses AS, for example
    funcname(value AS arg1, anothervalue AS arg2)

Pavel Stehule

Modified Files:
--------------
    pgsql/doc/src/sgml/ref:
        create_function.sgml (r1.87 -> r1.88)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/create_function.sgml?r1=1.87&r2=1.88)
    pgsql/doc/src/sgml:
        sources.sgml (r2.34 -> r2.35)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/sources.sgml?r1=2.34&r2=2.35)
        syntax.sgml (r1.136 -> r1.137)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/syntax.sgml?r1=1.136&r2=1.137)
        xfunc.sgml (r1.139 -> r1.140)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/xfunc.sgml?r1=1.139&r2=1.140)
    pgsql/src/backend/catalog:
        namespace.c (r1.118 -> r1.119)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/namespace.c?r1=1.118&r2=1.119)
        pg_aggregate.c (r1.102 -> r1.103)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/pg_aggregate.c?r1=1.102&r2=1.103)
        pg_proc.c (r1.167 -> r1.168)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/pg_proc.c?r1=1.167&r2=1.168)
    pgsql/src/backend/commands:
        aggregatecmds.c (r1.49 -> r1.50)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/aggregatecmds.c?r1=1.49&r2=1.50)
        functioncmds.c (r1.111 -> r1.112)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/functioncmds.c?r1=1.111&r2=1.112)
        tsearchcmds.c (r1.17 -> r1.18)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/tsearchcmds.c?r1=1.17&r2=1.18)
        typecmds.c (r1.137 -> r1.138)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/typecmds.c?r1=1.137&r2=1.138)
    pgsql/src/backend/nodes:
        copyfuncs.c (r1.441 -> r1.442)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c?r1=1.441&r2=1.442)
        equalfuncs.c (r1.364 -> r1.365)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/equalfuncs.c?r1=1.364&r2=1.365)
        nodeFuncs.c (r1.42 -> r1.43)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/nodeFuncs.c?r1=1.42&r2=1.43)
        outfuncs.c (r1.365 -> r1.366)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/outfuncs.c?r1=1.365&r2=1.366)
        readfuncs.c (r1.223 -> r1.224)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/readfuncs.c?r1=1.223&r2=1.224)
    pgsql/src/backend/optimizer/plan:
        planner.c (r1.256 -> r1.257)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planner.c?r1=1.256&r2=1.257)
    pgsql/src/backend/optimizer/util:
        clauses.c (r1.278 -> r1.279)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c?r1=1.278&r2=1.279)
    pgsql/src/backend/parser:
        gram.y (r2.681 -> r2.682)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y?r1=2.681&r2=2.682)
        parse_expr.c (r1.243 -> r1.244)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.243&r2=1.244)
        parse_func.c (r1.216 -> r1.217)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_func.c?r1=1.216&r2=1.217)
    pgsql/src/backend/utils/adt:
        regproc.c (r1.110 -> r1.111)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/regproc.c?r1=1.110&r2=1.111)
        ruleutils.c (r1.306 -> r1.307)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/ruleutils.c?r1=1.306&r2=1.307)
    pgsql/src/backend/utils/fmgr:
        funcapi.c (r1.45 -> r1.46)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/fmgr/funcapi.c?r1=1.45&r2=1.46)
    pgsql/src/include/catalog:
        catversion.h (r1.542 -> r1.543)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h?r1=1.542&r2=1.543)
        namespace.h (r1.59 -> r1.60)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/namespace.h?r1=1.59&r2=1.60)
    pgsql/src/include:
        funcapi.h (r1.29 -> r1.30)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/funcapi.h?r1=1.29&r2=1.30)
    pgsql/src/include/nodes:
        nodes.h (r1.227 -> r1.228)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/nodes.h?r1=1.227&r2=1.228)
        primnodes.h (r1.150 -> r1.151)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/primnodes.h?r1=1.150&r2=1.151)
    pgsql/src/include/parser:
        parse_func.h (r1.65 -> r1.66)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/parse_func.h?r1=1.65&r2=1.66)
    pgsql/src/test/regress/expected:
        polymorphism.out (r1.20 -> r1.21)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/polymorphism.out?r1=1.20&r2=1.21)
        rangefuncs.out (r1.22 -> r1.23)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/rangefuncs.out?r1=1.22&r2=1.23)
    pgsql/src/test/regress/sql:
        polymorphism.sql (r1.11 -> r1.12)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/polymorphism.sql?r1=1.11&r2=1.12)
        rangefuncs.sql (r1.11 -> r1.12)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/rangefuncs.sql?r1=1.11&r2=1.12)

pgsql-committers by date:

Previous
From: alvherre@postgresql.org (Alvaro Herrera)
Date:
Subject: pgsql: Make it possibly to specify GUC params per user and per database.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Update plhandler.sgml to describe validators and inline handlers