public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Tom Lane <[email protected]>
Cc: Jonathan S. Katz <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: Documentation for create unique index is insuficient and (because of that) incorrect
Date: Tue, 20 Nov 2018 15:08:31 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

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

view thread (11+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Documentation for create unique index is insuficient and (because of that) incorrect
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox