"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Personally my advice is to avoid USING: it wasn't one of the SQL
>>> committee's better ideas.
> There's no query you can write with USING that you can't write in a
> longer form with ON; but a query of moderate complexity can become
> significantly shorter with USING, and thus easier to understand and
> less prone to bugs than the ON form.
If USING (x) actually were exactly equivalent to ON (a.x = b.x),
I'd be less annoyed with it. But it isn't; the committee just
couldn't resist the urge to decorate it with some dubious additional
behaviors.
regards, tom lane
