aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-06-04 15:48:31 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-06-04 15:48:31 -0400
commit1c2af01b98c3aece7e5f6978137effcf06e8b81d (patch)
treece137b1e2ed40836e7a28694d5cda8a213ed1c1a /src/backend/access/gist/gistutil.c
parent918eb0f34f2af3e0d2823a164d22b6906d46dfcd (diff)
downloadpostgresql-1c2af01b98c3aece7e5f6978137effcf06e8b81d.tar.gz
postgresql-1c2af01b98c3aece7e5f6978137effcf06e8b81d.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/gistutil.c')
0 files changed, 0 insertions, 0 deletions