Re: Write Ahead Logging for Hash Indexes
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Jeff Janes <jeff.janes@gmail.com>,
Jesper Pedersen <jesper.pedersen@redhat.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2016-12-01T16:14:58Z
Lists: pgsql-hackers
On Thu, Dec 1, 2016 at 1:03 AM, Amit Kapila <amit.kapila16@gmail.com> wrote: > On Wed, Nov 9, 2016 at 7:40 PM, Amit Kapila <amit.kapila16@gmail.com> wrote: >> On Tue, Nov 8, 2016 at 10:56 PM, Jeff Janes <jeff.janes@gmail.com> wrote: >>> Unless we want to wait until that work is committed before doing more review >>> and testing on this. >> >> The concurrent hash index patch is getting changed and some of the >> changes needs change in this patch as well. So, I think after it gets >> somewhat stabilized, I will update this patch as well. > > Now that concurrent hash index patch is committed [1], I will work on > rebasing this patch. Note, I have moved this to next CF. Thanks. I am thinking that it might make sense to try to get the "microvacuum support for hash index" and "cache hash index meta page" patches committed before this one, because I'm guessing they are much simpler than this one, and I think therefore that the review of those patches can probably move fairly quickly. Of course, ideally I can also start reviewing this one in the meantime. Does that make sense to you? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Add a regression test for snapshot too old with hash indexes.
- 42bdaebf1618 10.0 landed
-
hash: Add write-ahead logging support.
- c11453ce0aea 10.0 landed
-
Improve coding in _hash_addovflpage.
- e898437460f5 10.0 cited
-
Remove _hash_wrtbuf() in favor of calling MarkBufferDirty().
- 25216c989384 10.0 cited
-
Improve hash index bucket split behavior.
- 6d46f4783efe 10.0 cited