aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/tsgistidx.c
diff options
context:
space:
mode:
authorDean Rasheed <dean.a.rasheed@gmail.com>2016-12-21 16:58:18 +0000
committerDean Rasheed <dean.a.rasheed@gmail.com>2016-12-21 16:58:18 +0000
commit58b1362642d47bd7a7ed1157035a38671555e860 (patch)
tree477488d4deb6a65200ce7cde0aca87f547492cc0 /src/backend/utils/adt/tsgistidx.c
parentcd510f04137a1436ad6029da4998f5224395a08d (diff)
downloadpostgresql-58b1362642d47bd7a7ed1157035a38671555e860.tar.gz
postgresql-58b1362642d47bd7a7ed1157035a38671555e860.zip
Fix order of operations in CREATE OR REPLACE VIEW.
When CREATE OR REPLACE VIEW acts on an existing view, don't update the view options until after the view query has been updated. This is necessary in the case where CREATE OR REPLACE VIEW is used on an existing view that is not updatable, and the new view is updatable and specifies the WITH CHECK OPTION. In this case, attempting to apply the new options to the view before updating its query fails, because the options are applied using the ALTER TABLE infrastructure which checks that WITH CHECK OPTION is only applied to an updatable view. If new columns are being added to the view, that is also done using the ALTER TABLE infrastructure, but it is important that that still be done before updating the view query, because the rules system checks that the query columns match those on the view relation. Added a comment to explain that, in case someone is tempted to move that to where the view options are now being set. Back-patch to 9.4 where WITH CHECK OPTION was added. Report: https://postgr.es/m/CAEZATCUp%3Dz%3Ds4SzZjr14bfct_bdJNwMPi-gFi3Xc5k1ntbsAgQ%40mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/tsgistidx.c')
0 files changed, 0 insertions, 0 deletions