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
commit3eef32c58b438e08071acb22580162976bce680b (patch)
treeb5b4c32ce1d3095744f624839d1fdba1ab0c9466
parent5527b79cc04a6aa3aab885d3bcd7162b4c620b1c (diff)
downloadpostgresql-3eef32c58b438e08071acb22580162976bce680b.tar.gz
postgresql-3eef32c58b438e08071acb22580162976bce680b.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>