From c1f91a38e20864c14650794a64d52f2d6c900e0f Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 19 Oct 2002 19:00:47 +0000 Subject: Fix rewrite code so that rules are in fact executed in order by name, rather than being reordered according to INSTEAD attribute for implementation convenience. Also, increase compiled-in recursion depth limit from 10 to 100 rewrite cycles. 10 seems pretty marginal for situations where multiple rules exist for the same query. There was a complaint about this recently, so I'm going to bump it up. (Perhaps we should make the limit a GUC parameter, but that's too close to being a new feature to do in beta.) --- doc/src/sgml/rules.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml index 50bcf3a4538..4b72d5de3b2 100644 --- a/doc/src/sgml/rules.sgml +++ b/doc/src/sgml/rules.sgml @@ -1,4 +1,4 @@ - + The Rule System @@ -1043,8 +1043,8 @@ CREATE RULE rule_name AS ON event in more or less parse trees. So the parse trees in the rule actions must have either another command type or another result relation. Otherwise this recursive process will end up in a loop. - There is a compiled in recursion limit of currently 10 iterations. - If after 10 iterations there are still update rules to apply the + There is a compiled-in 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. -- cgit v1.2.3