Re: Documentation for create unique index is insuficient and (because of that) incorrect
От | Tom Lane |
---|---|
Тема | Re: Documentation for create unique index is insuficient and (because of that) incorrect |
Дата | |
Msg-id | 25342.1542736665@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Documentation for create unique index is insuficient and (because of that) incorrect (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Documentation for create unique index is insuficient and(because of that) incorrect
|
Список | pgsql-docs |
I wrote: > "Jonathan S. Katz" <jkatz@postgresql.org> writes: >> Also +1 on having a section on covering indexes. > I see Alvaro is on the same page here. I'll go write something > later today. So looking closer ... not only is the unique-index section not a very good fit, but there is already a section that this does fit into pretty well, which is 11.11 on index-only scans. Not only do you need to understand index-only scans to understand why you'd want INCLUDE, but there's already discussion there of making covering indexes the hard way. So what I think I should do is reformulate that discussion to talk about making covering indexes with INCLUDE, and then mention in passing that you can also do it without that as long as you don't mind the payload columns being part of the index semantics. I'm also wondering whether to move that section someplace earlier in chapter 11. Right now it's near the end because it's mostly info about an implementation detail; but it wouldn't be hard to make the argument that covering indexes are more important than, say, indexes with custom collations. Should we move it, and if so to where? regards, tom lane
В списке pgsql-docs по дате отправления: