pgsql: Fix dumping of views that are just VALUES(...) but have column a - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix dumping of views that are just VALUES(...) but have column a
Date
Msg-id E1YQfLA-0005N4-U3@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix dumping of views that are just VALUES(...) but have column aliases.

The "simple" path for printing VALUES clauses doesn't work if we need
to attach nondefault column aliases, because there's noplace to do that
in the minimal VALUES() syntax.  So modify get_simple_values_rte() to
detect nondefault aliases and treat that as a non-simple case.  This
further exposes that the "non-simple" path never actually worked;
it didn't produce valid syntax.  Fix that too.  Per bug #12789 from
Curtis McEnroe, and analysis by Andrew Gierth.

Back-patch to all supported branches.  Before 9.3, this also requires
back-patching the part of commit 092d7ded29f36b0539046b23b81b9f0bf2d637f1
that created get_simple_values_rte() to begin with; inserting the extra
test into the old factorization of that logic would've been too messy.

Branch
------
master

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

Modified Files
--------------
src/backend/utils/adt/ruleutils.c   |   39 ++++++++++++++++++++++---
src/test/regress/expected/rules.out |   54 +++++++++++++++++++++++++++++++++++
src/test/regress/sql/rules.sql      |   18 ++++++++++++
3 files changed, 107 insertions(+), 4 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix dumping of views that are just VALUES(...) but have column a
Next
From: Tom Lane
Date:
Subject: pgsql: Fix dumping of views that are just VALUES(...) but have column a