Horton

Re: Page Scan Mode in Hash Index

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Ashutosh Sharma <ashu.coek88@gmail.com>
Cc: Jesper Pedersen <jesper.pedersen@redhat.com>, Amit Kapila <amit.kapila16@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-09-21T04:00:12Z
Lists: pgsql-hackers 
On Wed, Sep 20, 2017 at 11:43 AM, Ashutosh Sharma <ashu.coek88@gmail.com> wrote:
> Attached are the patches with above changes. Thanks.

Thanks.  I think that the comments and README changes in 0003 need
significantly more work.  In several places, they fail to note the
unlogged vs. logged differences, and the header comment for
hashbucketcleanup still says that scans depend on increasing-TID order
(really, 0001 should change that text somehow).

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Remove lsn from HashScanPosData.

  2. Fix trivial mistake in README.

  3. hash: Implement page-at-a-time scan.

  4. Reduce pinning and buffer content locking for btree scans.