Horton

Re: Minmax indexes

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Erik Rijkers <er@xs4all.nl>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2013-09-26T17:40:43Z
Lists: pgsql-hackers 
Erik Rijkers wrote:

> I have the impression it's not quite working correctly.
> 
> The attached program returns different results for different values of enable_bitmapscan (consistently).

Clearly there's some bug somewhere.  I'll investigate it more.

> ( Btw, I had to make the max_locks_per_transaction higher for even not-so-large tables -- is that expected?  For a 100M row
> table, max_locks_per_transaction=1024 was not enough; I set it to 2048.  Might be worth some documentation, eventually. )

Not documentation -- that would also be a bug which needs to be fixed.

Thanks for testing.

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

Commits

  1. Refactor per-page logic common to all redo routines to a new function.

  2. Reduce use of heavyweight locking inside hash AM.

  3. Scan the buffer pool just once, not once per fork, during relation drop.

  4. Major patch from Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>