aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2011-06-13 12:59:04 -0400
committerRobert Haas <rhaas@postgresql.org>2011-06-13 13:00:09 -0400
commit26e7eec5f07c5dfb4b57f374bf01185edd88cf73 (patch)
tree2615d1333c044b11f558a874a967e6aa8bfca7ab
parentf2328b0713b175b0d49651fb7ec807e7174e92aa (diff)
downloadpostgresql-26e7eec5f07c5dfb4b57f374bf01185edd88cf73.tar.gz
postgresql-26e7eec5f07c5dfb4b57f374bf01185edd88cf73.zip
Clarify that NATURAL without matching columns is like CROSS JOIN.
As suggested by Grzegorz Szpetkowski.
-rw-r--r--doc/src/sgml/queries.sgml4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml
index b3cf39a39b0..7ca640e6975 100644
--- a/doc/src/sgml/queries.sgml
+++ b/doc/src/sgml/queries.sgml
@@ -266,7 +266,9 @@ FROM <replaceable>table_reference</replaceable> <optional>, <replaceable>table_r
<literal>USING</>: it forms a <literal>USING</> list
consisting of all column names that appear in both
input tables. As with <literal>USING</>, these columns appear
- only once in the output table.
+ only once in the output table. If there are no common
+ columns, <literal>NATURAL</literal> behaves like
+ <literal>CROSS JOIN</literal>.
</para>
<para>