DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:from:date:message-id:subject:to:content-type;
	b=ZAvLkNIQhMlwLBfKQNRl+MaRupjTXKywZxtEqXDGrfDCnddMrsYruTUzUEOmPzJ/KN
	Por7ZqJ1+z/MYuCrDyXNamM5jSgi2SFgFnHU6X4yhq8ISirbzoVepvEqzRWuTl5FlCLZ
	PxEjgS1tSIPiJwUU9TPD0k52rgdm7eWQ3/JOI=
MIME-Version: 1.0
From: Josh Kupershmidt <schmiddy@gmail.com>
Date: Wed, 17 Mar 2010 10:38:59 -0400
Message-ID: <4ec1cf761003170738m5ec60f66o37676c7c939d0b79@mail.gmail.com>
Subject: Incorrect SQL on CREATE INDEX page
To: pgsql-docs@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1

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. Correct syntax should be:
    CREATE INDEX gin_idx ON documents_table USING gin(locations) WITH
(fastupdate = off);

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?

Josh