| From: | "John Huttley" <john(at)mwk(dot)co(dot)nz> |
|---|---|
| To: | "Bruce Momjian" <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "pgsql-general" <pgsql-general(at)postgreSQL(dot)org> |
| Subject: | Re: [GENERAL] Limitation |
| Date: | 1999-06-24 21:53:37 |
| Message-ID: | 008901bebe8c$04c6f840$1401a8c0@Mr_Creosote.MWK.co.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
The answer is that you are thinking as indexes in the context of fast lookup
on fields.
However my requirement comes from a need to ensure that every single field
in the
table forms a unique combination. (not my design, I might add)
Now you know why, can you append it to the TODO list?
On thinking about it, I wonder if the same field can appear more than
once in an index. Now that would be weird!
>> 1. Have more than 7 fields on a btree index
>
>We have never understood why someone would want an index with more than
>seven columns.
>
>--
> Bruce Momjian | http://www.op.net/~candle
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Huttley | 1999-06-24 22:04:35 | Re: [GENERAL] Limitation |
| Previous Message | Hub.Org News Admin | 1999-06-24 21:33:42 |