aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2022-09-28 13:14:38 -0400
committerBruce Momjian <bruce@momjian.us>2022-09-28 13:14:38 -0400
commit2a66b9bfb74e522d64c066dabe4fddde0fe7425c (patch)
treee26ba93e8fffd958934d98082bff48ec2ecb29a3
parentf77becbe5a99c9853b1ae7f22aa15babd01368b7 (diff)
downloadpostgresql-2a66b9bfb74e522d64c066dabe4fddde0fe7425c.tar.gz
postgresql-2a66b9bfb74e522d64c066dabe4fddde0fe7425c.zip
doc: clarify internal behavior of RECURSIVE CTE queries
Reported-by: Tom Lane Discussion: https://postgr.es/m/3976627.1662651004@sss.pgh.pa.us Backpatch-through: 10
-rw-r--r--doc/src/sgml/queries.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml
index 4c5a83c9cbf..95559ef1ac4 100644
--- a/doc/src/sgml/queries.sgml
+++ b/doc/src/sgml/queries.sgml
@@ -2173,7 +2173,7 @@ SELECT sum(n) FROM t;
<note>
<para>
While <literal>RECURSIVE</literal> allows queries to be specified
- recursively, internally all queries are evaluated iteratively.
+ recursively, internally such queries are evaluated iteratively.
</para>
</note>