aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeProjectSet.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-07-24 15:16:31 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2017-07-24 15:16:31 -0400
commitb4af9e3f378ef56fa48b98a0bfb641900b0280dc (patch)
treedfa7ea96453a9f43bdd04e957acd901e527fc185 /src/backend/executor/nodeProjectSet.c
parent278cb4341103e967189997985b09981a73e23a34 (diff)
downloadpostgresql-b4af9e3f378ef56fa48b98a0bfb641900b0280dc.tar.gz
postgresql-b4af9e3f378ef56fa48b98a0bfb641900b0280dc.zip
Ensure that pg_get_ruledef()'s output matches pg_get_viewdef()'s.
Various cases involving renaming of view columns are handled by having make_viewdef pass down the view's current relation tupledesc to get_query_def, which then takes care to use the column names from the tupledesc for the output column names of the SELECT. For some reason though, we'd missed teaching make_ruledef to do similarly when it is printing an ON SELECT rule, even though this is exactly the same case. The results from pg_get_ruledef would then be different and arguably wrong. In particular, this breaks pre-v10 versions of pg_dump, which in some situations would define views by means of emitting a CREATE RULE ... ON SELECT command. Third-party tools might not be happy either. In passing, clean up some crufty code in make_viewdef; we'd apparently modernized the equivalent code in make_ruledef somewhere along the way, and missed this copy. Per report from Gilles Darold. Back-patch to all supported versions. Discussion: https://postgr.es/m/ec05659a-40ff-4510-fc45-ca9d965d0838@dalibo.com
Diffstat (limited to 'src/backend/executor/nodeProjectSet.c')
0 files changed, 0 insertions, 0 deletions