We haven't had a fixed limit on rule recursion depth since 7.3 ...

but the documentation still said so.

diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml
index c5fb9529122789cb01d1548709479284f0c2e3b4..57c30824bfdac065fab46b7711359107a79e39df 100644 (file)
--- a/doc/src/sgml/rules.sgml
+++ b/doc/src/sgml/rules.sgml
@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/rules.sgml,v 1.31 2003/11/01 01:56:29 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/rules.sgml,v 1.31.2.1 2005/01/29 23:46:16 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>