summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane2005-01-29 23:45:53 +0000
committerTom Lane2005-01-29 23:45:53 +0000
commit426ccf86fa6207f0715b576fe694339a45a12066 (patch)
tree942b27ae4aa8849a6dcf0f8af059cde0c97ebb07
parentd2190ad66e72b342840ad480ba9624a109a91eed (diff)
We haven't had a fixed limit on rule recursion depth since 7.3 ...
but the documentation still said so.
-rw-r--r--doc/src/sgml/rules.sgml13
1 files changed, 6 insertions, 7 deletions
diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml
index f337bccdd4d..4be1dc5e467 100644
--- a/doc/src/sgml/rules.sgml
+++ b/doc/src/sgml/rules.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.37.4.3 2005/01/23 00:37:23 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.37.4.4 2005/01/29 23:45:53 tgl Exp $ -->
<chapter id="rules">
<title>The Rule System</title>
@@ -1000,12 +1000,11 @@ CREATE RULE <replaceable>rule_name</> AS ON <replaceable>event</>
The query trees generated from rule actions are thrown into the
rewrite system again, and maybe more rules get applied resulting
in more or less query trees.
- So the query trees in the rule actions must have either a different command type
- or a different result relation, otherwise, this recursive process will end up in a loop.
- There is a fixed recursion limit of currently 100 iterations.
- If after 100 iterations there are still update rules to apply, the
- rule system assumes a loop over multiple rule definitions and reports
- an error.
+ So a rule's actions must have either a different
+ command type or a different result relation than the rule itself is
+ on, otherwise this recursive process will end up in an infinite loop.
+ (Recursive expansion of a rule will be detected and reported as an
+ error.)
</para>
<para>