From: | "Roderick A(dot) Anderson" <raanders(at)cyber-office(dot)net> |
---|---|
To: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Incorrect SQL on CREATE INDEX page |
Date: | 2010-03-17 15:38:06 |
Message-ID: | 4BA0F75E.6060903@cyber-office.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Tom Lane wrote:
> Josh Kupershmidt <schmiddy(at)gmail(dot)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
--
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2010-03-17 18:04:12 | Re: The type of ssl_renegotiation_limit |
Previous Message | Tom Lane | 2010-03-17 15:13:45 | Re: Incorrect SQL on CREATE INDEX page |