Date: Thu, 16 Mar 2017 16:12:14 -0400
From: Bruce Momjian <bruce@momjian.us>
To: mnikulyak@gmail.com
Cc: pgsql-docs@postgresql.org
Subject: Re: Excluding common values from the index
Message-ID: <20170316201214.GB32733@momjian.us>
References: <20170311230031.1429.23255@wrigleys.postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170311230031.1429.23255@wrigleys.postgresql.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On Sat, Mar 11, 2017 at 11:00:31PM +0000, mnikulyak@gmail.com wrote:
> The following documentation comment has been logged on the website:
> 
> Page: https://www.postgresql.org/docs/9.6/static/indexes-partial.html
> Description:
> 
> Rather than a report of an error, this letter is a suggestion of improvement
> of PostgreSQL.
> 
> As per page https://www.postgresql.org/docs/9.6/static/indexes-partial.html,
> PostgreSQL avoids using indices when retrieving common values.
> 
> Then, maybe, during the construction of an index, PostgreSQL should be
> detecting such common values, and exclude them from the index automatically.

That is an interesting idea, but what happens if the table changes and
those values become rare?  How would we adjust for that?  What if the
table is empty when the index is created?  How would we detect common
values?

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs