DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	b=QVCYwkwL5NQ1o2gVlUu/RfC6bCucrLAMu9/bE1FgHV4l5SDbvX/6GeTaBA+02QoZFw
	bOh1Y/PrjRBx0aZ+w0ojfPZTxq9tHOwOCSRevakUdzVRaGk4PtLJd9mgdMJBcS0C0peW
	/8p/+cbvnC2HymMsnbIcK1ue4iKYe0wjXcaFg=
MIME-Version: 1.0
Date: Wed, 18 May 2011 03:47:00 +0200
Message-ID: <BANLkTimtKpbzfd9mQM_R5=0VnTfc=gF0qQ@mail.gmail.com>
Subject: 7.2. Table Expressions suggestion about NATURAL JOIN
From: Grzegorz Szpetkowski <gszpetkowski@gmail.com>
To: pgsql-docs@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1

http://www.postgresql.org/docs/9.0/static/queries-table-expressions.html
http://www.postgresql.org/docs/9.0/static/sql-select.html

Respectively:

"Finally, NATURAL is a shorthand form of USING: it forms a USING list
consisting of all column names that appear in both input tables. As
with USING, these columns appear only once in the output table."

and

"NATURAL is shorthand for a USING list that mentions all columns in
the two tables that have the same names."

To make that comprehensive you can add something like: "Note that if
there is no any "shared" column between tables, then NATURAL JOIN acts
like ON TRUE (that is, tables are cross-joined)", because it's not
obvious.

thanks & regards,
greg szpetkowski