Horton

Re: pgsql 10: hash indexes testing

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: AP <ap@zip.com.au>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-07-11T17:38:07Z
Lists: pgsql-hackers 
Amit Kapila wrote:

> Yes, I also think the same idea can be used, in fact, I have mentioned
> it [1] as soon as you have committed that patch.  Do we want to do
> anything at this stage for PG-10?  I don't think we should attempt
> something this late unless people feel this is a show-stopper issue
> for usage of hash indexes.  If required, I think a separate function
> can be provided to allow users to perform squeeze operation.

Sorry, I have no idea how critical this squeeze thing is for the
newfangled hash indexes, so I cannot comment on that.  Does this make
the indexes unusable in some way under some circumstances?

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

Commits

  1. pgstatindex: Insert some casts to prevent overflow.

  2. hash: Immediately after a bucket split, try to clean the old bucket.

  3. hash: Increase the number of possible overflow bitmaps by 8x.

  4. BRIN auto-summarization