From 8545b28679a2ec2aa66ad2ec81f17019dab5d780 Mon Sep 17 00:00:00 2001 From: Dean Rasheed Date: Mon, 4 Mar 2024 10:48:40 +0000 Subject: [PATCH] Fix doc omission for MERGE into updatable views. Commit 5f2e179bd3 missed one place in rules.sgml that should have mentioned MERGE. Also, be more specific when saying that MERGE doesn't support rules, since it does support SELECT rules. --- doc/src/sgml/rules.sgml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml index 784c16e76ea..7a928bd7b90 100644 --- a/doc/src/sgml/rules.sgml +++ b/doc/src/sgml/rules.sgml @@ -859,7 +859,8 @@ SELECT t1.a, t2.b, t1.ctid FROM t1, t2 WHERE t1.a = t2.a; a view. These rules will rewrite the command, typically into a command that updates one or more tables, rather than views. That is the topic of . Note that this will not work with - MERGE, which currently does not support rules. + MERGE, which currently does not support rules on + the target relation other than SELECT rules. @@ -873,7 +874,8 @@ SELECT t1.a, t2.b, t1.ctid FROM t1, t2 WHERE t1.a = t2.a; Automatic rewriting of an INSERT, - UPDATE, or DELETE query on a + UPDATE, DELETE, or + MERGE query on a simple view is always tried last. Therefore, if a view has rules or triggers, they will override the default behavior of automatically updatable views.