Re: Documentation for create unique index is insuficient and (because of that) incorrect

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, emilioplatzer(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Documentation for create unique index is insuficient and (because of that) incorrect
Date: 2018-11-20 18:08:31
Message-ID: 20181120180831.frne3ck56mfdh573@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On 2018-Nov-20, Tom Lane wrote:

> 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.

That seems sensible.

> 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?

I think right next to 11.5, which currently completes the topic of how
are indexes used, is a good place.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Jonathan S. Katz 2018-11-20 18:13:51 Re: Documentation for create unique index is insuficient and (because of that) incorrect
Previous Message Tom Lane 2018-11-20 17:57:45 Re: Documentation for create unique index is insuficient and (because of that) incorrect