rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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

but the documentation still said so.
This commit is contained in:
Tom Lane 2005-01-29 23:45:36 +00:00
parent b7d236d663
commit 5703a69003
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/src/sgml/rules.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.40 2005/01/23 00:30:18 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.41 2005/01/29 23:45:36 tgl Exp $ -->
<chapter id="rules"> <chapter id="rules">
<title>The Rule System</title> <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 The query trees generated from rule actions are thrown into the
rewrite system again, and maybe more rules get applied resulting rewrite system again, and maybe more rules get applied resulting
in more or less query trees. in more or less query trees.
So the query trees in the rule actions must have either a different command type So a rule's actions must have either a different
or a different result relation, otherwise, this recursive process will end up in a loop. command type or a different result relation than the rule itself is
There is a fixed recursion limit of currently 100 iterations. on, otherwise this recursive process will end up in an infinite loop.
If after 100 iterations there are still update rules to apply, the (Recursive expansion of a rule will be detected and reported as an
rule system assumes a loop over multiple rule definitions and reports error.)
an error.
</para> </para>
<para> <para>