Date: Tue, 20 Nov 2018 15:08:31 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>,
	Bruce Momjian <bruce@momjian.us>, emilioplatzer@gmail.com,
	pgsql-docs@lists.postgresql.org
Subject: Re: Documentation for create unique index is insuficient and
 (because of that) incorrect
Message-ID: <20181120180831.frne3ck56mfdh573@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <25342.1542736665@sss.pgh.pa.us>
User-Agent: NeoMutt/20180716
Precedence: bulk

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