Horton

Re: Write Ahead Logging for Hash Indexes

Amit Kapila <amit.kapila16@gmail.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila16@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jeff Janes <jeff.janes@gmail.com>, Jesper Pedersen <jesper.pedersen@redhat.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2016-12-27T06:58:25Z
Lists: pgsql-hackers

Attachments

On Fri, Dec 23, 2016 at 6:40 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> On Thu, Dec 22, 2016 at 9:56 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Mon, Dec 5, 2016 at 2:46 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>>>> I'll review after that, since I have other things to review meanwhile.
>>>
>>> Attached, please find the rebased patch attached with this e-mail.
>>> There is no fundamental change in patch except for adapting the new
>>> locking strategy in squeeze operation.  I have done the sanity testing
>>> of the patch with master-standby setup and Kuntal has helped me to
>>> verify it with his wal-consistency checker patch.
>>
>> This patch again needs a rebase,
>>
>
> I had completed it yesterday night and kept it for night long tests to
> check the sanity of the patch, but I guess now I need another rebase.
>

After recent commit's 7819ba1e and 25216c98, this patch requires a
rebase.  Attached is the rebased patch.


-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Commits

  1. Add a regression test for snapshot too old with hash indexes.

  2. hash: Add write-ahead logging support.

  3. Improve coding in _hash_addovflpage.

  4. Remove _hash_wrtbuf() in favor of calling MarkBufferDirty().

  5. Improve hash index bucket split behavior.