Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 5703a69

Browse files
committed
We haven't had a fixed limit on rule recursion depth since 7.3 ...
but the documentation still said so.
1 parent b7d236d commit 5703a69

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

doc/src/sgml/rules.sgml

+6-7
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.40 2005/01/23 00:30:18 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.41 2005/01/29 23:45:36 tgl Exp $ -->
22

33
<chapter id="rules">
44
<title>The Rule System</title>
@@ -1000,12 +1000,11 @@ CREATE RULE <replaceable>rule_name</> AS ON <replaceable>event</>
10001000
The query trees generated from rule actions are thrown into the
10011001
rewrite system again, and maybe more rules get applied resulting
10021002
in more or less query trees.
1003-
So the query trees in the rule actions must have either a different command type
1004-
or a different result relation, otherwise, this recursive process will end up in a loop.
1005-
There is a fixed recursion limit of currently 100 iterations.
1006-
If after 100 iterations there are still update rules to apply, the
1007-
rule system assumes a loop over multiple rule definitions and reports
1008-
an error.
1003+
So a rule's actions must have either a different
1004+
command type or a different result relation than the rule itself is
1005+
on, otherwise this recursive process will end up in an infinite loop.
1006+
(Recursive expansion of a rule will be detected and reported as an
1007+
error.)
10091008
</para>
10101009

10111010
<para>

0 commit comments

Comments
 (0)