| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Eugene Wang <eugenewangfw(at)gmail(dot)com> |
| Cc: | Martín Marqués <martin(dot)marques(at)2ndquadrant(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org, PG Doc comments form <noreply(at)postgresql(dot)org> |
| Subject: | Re: Mistakes between an example and its description |
| Date: | 2018-05-10 19:09:54 |
| Message-ID: | 20180510190954.3ww3kkea3bcpw3be@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Eugene Wang wrote:
> Unique Constraint and Unique Index should be the same in this single-column
> case, right?
>
> Because, according to CONSTRAINT page in Postgres Documentation, Unique
> Constraint on single column is realized as Unique B-TREE index.
>
> I have just realized that it is still a btree index, but I think this
> example is not exactly a regular btree example. At least I will put the
> example as: CREATE INDEX title_idx ON films USING BTREE(title);
Yeah, I see no point for having UNIQUE in that example.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martín Marqués | 2018-05-10 19:16:43 | Re: Mistakes between an example and its description |
| Previous Message | Eugene Wang | 2018-05-10 19:04:35 | Re: Mistakes between an example and its description |