pgsql: When a function not returning RECORD has a single OUT parameter,

Log Message:
-----------
When a function not returning RECORD has a single OUT parameter, use
the parameter's name (if any) as the default column name for SELECT FROM
the function, rather than the function name as previously. I still think
this is a bad idea, but I lost the argument. Force decompilation of
function RTEs to specify full aliases always, to reduce the odds of this
decision breaking dumped views.

Modified Files:
--------------
pgsql/src/backend/parser:
parse_relation.c (r1.113 -> r1.114)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_relation.c.diff?r1=1.113&r2=1.114)
pgsql/src/backend/utils/adt:
ruleutils.c (r1.205 -> r1.206)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/ruleutils.c.diff?r1=1.205&r2=1.206)
pgsql/src/backend/utils/fmgr:
funcapi.c (r1.24 -> r1.25)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/fmgr/funcapi.c.diff?r1=1.24&r2=1.25)
pgsql/src/include:
funcapi.h (r1.18 -> r1.19)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/funcapi.h.diff?r1=1.18&r2=1.19)
pgsql/src/test/regress/expected:
plpgsql.out (r1.39 -> r1.40)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/plpgsql.out.diff?r1=1.39&r2=1.40)
rangefuncs.out (r1.13 -> r1.14)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/rangefuncs.out.diff?r1=1.13&r2=1.14)