Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 244A0659C83
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Wed, 17 Mar 2010 12:59:46 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 11824-08 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Wed, 17 Mar 2010 15:59:34 +0000 (UTC)
X-Greylist: delayed 00:21:26.944632 by SQLgrey-1.7.6
Received: from mx0.cyber-office.net (mx0.cyber-office.net [98.143.112.36])
	by mail.postgresql.org (Postfix) with ESMTP id 77A65632D9B
	for <pgsql-docs@postgresql.org>; Wed, 17 Mar 2010 12:59:35 -0300 (ADT)
Received: from phoenix.anderson.home (hugin.cyber-office.net [98.143.120.88])
	by mx0.cyber-office.net (Postfix) with ESMTP id B86CF12FE82
	for <pgsql-docs@postgresql.org>; Wed, 17 Mar 2010 08:38:06 -0700 (PDT)
Message-ID: <4BA0F75E.6060903@cyber-office.net>
Date: Wed, 17 Mar 2010 08:38:06 -0700
From: "Roderick A. Anderson" <raanders@cyber-office.net>
User-Agent: Thunderbird 2.0.0.22 (X11/20090625)
MIME-Version: 1.0
To: pgsql-docs@postgresql.org
Subject: Re: Incorrect SQL on CREATE INDEX page
References: <4ec1cf761003170738m5ec60f66o37676c7c939d0b79@mail.gmail.com>
	<28693.1268838825@sss.pgh.pa.us>
In-Reply-To: <28693.1268838825@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5
	tests=BAYES_00=-2.599
X-Spam-Level: 
X-Archive-Number: 201003/12
X-Sequence-Number: 5377

Tom Lane wrote:
> Josh Kupershmidt <schmiddy@gmail.com> writes:
<snip />
>> Also, a more minor quibble about the same section: the first example says:
>>     To create a B-tree index on the column title  in the table films:
>>     CREATE UNIQUE INDEX title_idx ON films (title);
>> Perhaps the mention of "B-tree" should be omitted here, since "USING
>> btree" is not actually used in the SQL provided. Or is there an
>> explicit guarantee that CREATE UNIQUE INDEX will always use a B-Tree
>> documented somewhere?
> 
> It's pointed out further up the page that btree is the default access
> method.

Maybe change it to  " ... B-tree index (the default) on the column ... " 
for those of us with short memories.


\\||/
Rod
--