Thread: pgsql/src/backend/executor (execFlatten.c execQual.c execScan.c functions.c nodeAgg.c nodeGroup.c nodeHash.c nodeHashjoin.c nodeIndexscan.c nodeMergejoin.c nodeNestloop.c nodeResult.c nodeSubplan.c nodeTidscan.c)

pgsql/src/backend/executor (execFlatten.c execQual.c execScan.c functions.c nodeAgg.c nodeGroup.c nodeHash.c nodeHashjoin.c nodeIndexscan.c nodeMergejoin.c nodeNestloop.c nodeResult.c nodeSubplan.c nodeTidscan.c)

From

Tom Lane

Date:

24 August 2000, 02:33:33

  Date: Wednesday, August 23, 2000 @ 23:29:04
Author: tgl

Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/executor
     from hub.org:/home/projects/pgsql/tmp/cvs-serv74772/backend/executor

Modified Files:
    execFlatten.c execQual.c execScan.c functions.c nodeAgg.c
    nodeGroup.c nodeHash.c nodeHashjoin.c nodeIndexscan.c
    nodeMergejoin.c nodeNestloop.c nodeResult.c nodeSubplan.c
    nodeTidscan.c

-----------------------------  Log Message  -----------------------------

SQL-language functions are now callable in ordinary fmgr contexts ...
for example, an SQL function can be used in a functional index.  (I make
no promises about speed, but it'll work ;-).)  Clean up and simplify
handling of functions returning sets.