diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-06-04 15:48:17 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-06-04 15:48:17 -0400 |
commit | a9143774958e861dc1e2c198ad4c0a4a6d0b9800 (patch) | |
tree | 7a7bd8f49be2c33103ad34c13ac5e3fc48439aab /src/backend/access/gist/gist.c | |
parent | 048417511aef8d5fb2d541b17b73afc730935cd5 (diff) | |
download | postgresql-a9143774958e861dc1e2c198ad4c0a4a6d0b9800.tar.gz postgresql-a9143774958e861dc1e2c198ad4c0a4a6d0b9800.zip |
Expose the "*VALUES*" alias that we generate for a stand-alone VALUES list.
We were trying to make that strictly an internal implementation detail,
but it turns out that it's exposed anyway when dumping a view defined
like
CREATE VIEW test_view AS VALUES (1), (2), (3) ORDER BY 1;
This comes out as
CREATE VIEW ... ORDER BY "*VALUES*".column1;
which fails to parse when reloading the dump.
Hacking ruleutils.c to suppress the column qualification looks like it'd
be a risky business, so instead promote the RTE alias to full-fledged
usability.
Per bug #6049 from Dylan Adams. Back-patch to all supported branches.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions