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
commit92cad1439f2b775211d34c7b8f42b87e02c68ace (patch)
tree411a612e0216f309f2b5ee710b4998a966c3fb11
parentdf92bc115ec8712cfdd0c7a26ef20b11914ab0a2 (diff)
downloadpostgresql-92cad1439f2b775211d34c7b8f42b87e02c68ace.tar.gz
postgresql-92cad1439f2b775211d34c7b8f42b87e02c68ace.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 42859aec422..33460da7db7 100644
--- a/doc/src/sgml/queries.sgml
+++ b/doc/src/sgml/queries.sgml
@@ -2110,9 +2110,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>