From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Incorrect SQL on CREATE INDEX page |
Date: | 2010-03-17 15:13:45 |
Message-ID: | 28693.1268838825@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Josh Kupershmidt <schmiddy(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Roderick A. Anderson | 2010-03-17 15:38:06 | Re: Incorrect SQL on CREATE INDEX page |
Previous Message | Josh Kupershmidt | 2010-03-17 14:38:59 | Incorrect SQL on CREATE INDEX page |