Band-aid fix for incorrect use of view options as StdRdOptions.
We really ought to make StdRdOptions and the other decoded forms of
reloptions self-identifying, but for the moment, assume that only plain
relations could possibly be user_catalog_tables. Fixes problem with bogus
"ON CONFLICT is not supported on table ... used as a catalog table" error
when target is a view with cascade option.
Discussion: <26681.1477940227@sss.pgh.pa.us>
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/e3e66d8a9813d22c2aa027d8f373a96d4d4c1b15
Modified Files
--------------
src/include/utils/rel.h | 3 ++-
src/test/regress/expected/insert_conflict.out | 24 ++++++++++++++++++++++++
src/test/regress/sql/insert_conflict.sql | 18 ++++++++++++++++++
3 files changed, 44 insertions(+), 1 deletion(-)
