To: Josh Kupershmidt <schmiddy@gmail.com>
cc: pgsql-docs@postgresql.org
Subject: Re: Incorrect SQL on CREATE INDEX page 
In-reply-to: <4ec1cf761003170738m5ec60f66o37676c7c939d0b79@mail.gmail.com> 
References: <4ec1cf761003170738m5ec60f66o37676c7c939d0b79@mail.gmail.com>
Comments: In-reply-to Josh Kupershmidt <schmiddy@gmail.com>
	message dated "Wed, 17 Mar 2010 10:38:59 -0400"
Date: Wed, 17 Mar 2010 11:13:45 -0400
Message-ID: <28693.1268838825@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Josh Kupershmidt <schmiddy@gmail.com> writes:
> In the "Examples" section of the page for CREATE INDEX:
> http://www.postgresql.org/docs/current/static/sql-createindex.html
> it says:
>    To create a GIN index with fast updates disabled:
>    CREATE INDEX gin_idx ON documents_table (locations) WITH (fastupdate = off);

> This SQL fails with 'ERROR:  unrecognized parameter "fastupdate"', as
> it is missing the USING clause.

Ooops.  You're right, that's definitely a mistake.  Will fix.

> 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.

			regards, tom lane