pgsql: Improve generated column names for cases involving sub-SELECTs. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Improve generated column names for cases involving sub-SELECTs.
Date
Msg-id E1RA3sr-00056J-36@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Improve generated column names for cases involving sub-SELECTs.

We'll now use "exists" for EXISTS(SELECT ...), "array" for ARRAY(SELECT
...), or the sub-select's own result column name for a simple expression
sub-select.  Previously, you usually got "?column?" in such cases.

Marti Raudsepp, reviewed by Kyotaro Horiugchi

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5ec6b7f1b87f0fa006b8e08a11cd4e99bcb67358

Modified Files
--------------
doc/src/sgml/ref/select.sgml             |    5 ++-
doc/src/sgml/syntax.sgml                 |    6 ++--
src/backend/parser/parse_target.c        |   42 ++++++++++++++++++++++++++++++
src/test/regress/expected/aggregates.out |    6 ++--
src/test/regress/expected/subselect.out  |   12 ++++----
src/test/regress/expected/with.out       |    4 +-
6 files changed, 59 insertions(+), 16 deletions(-)


pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: pgsql: In pg_upgrade, remove unnecessary local variable.
Next
From: Tom Lane
Date:
Subject: pgsql: Restructure error handling in reading of postgresql.conf.