aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2022-09-02 21:57:41 -0400
committerBruce Momjian <bruce@momjian.us>2022-09-02 21:57:41 -0400
commit170704da68c5150776c0ee4ed51350acde47b4a5 (patch)
tree8d8e4f7b46212fa799a46a7c5925f8fd9ca2cc58
parent4ddcb20592270ac3aa1082531d8057ca3d229951 (diff)
downloadpostgresql-170704da68c5150776c0ee4ed51350acde47b4a5.tar.gz
postgresql-170704da68c5150776c0ee4ed51350acde47b4a5.zip
doc: clarify recursion internal behavior
Reported-by: Drew DeVault Discussion: https://postgr.es/m/20211018091720.31299-1-sir@cmpwn.com Backpatch-through: 10
-rw-r--r--doc/src/sgml/queries.sgml5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml
index 1428d99d0f8..4c5a83c9cbf 100644
--- a/doc/src/sgml/queries.sgml
+++ b/doc/src/sgml/queries.sgml
@@ -2172,9 +2172,8 @@ SELECT sum(n) FROM t;
<note>
<para>
- Strictly speaking, this process is iteration not recursion, but
- <literal>RECURSIVE</literal> is the terminology chosen by the SQL standards
- committee.
+ While <literal>RECURSIVE</literal> allows queries to be specified
+ recursively, internally all queries are evaluated iteratively.
</para>
</note>