Re: Write Ahead Logging for Hash Indexes

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Write Ahead Logging for Hash Indexes
Date: 2016-08-30 02:23:48
Message-ID: CAA4eK1KtLcd0Ej_8wAJcYDugAFGngHwfOXU6s1AuzTHSyqmFxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 30, 2016 at 3:40 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Amit Kapila wrote:
>
>> How about attached?
>
> That works; pushed.

Thanks.

> (I removed a few #includes from the new file.)
>

oops, copied from hash.h and forgot to remove those.

>> If you want, I think we can one step further and move hash_redo to a
>> new file hash_xlog.c which is required for main patch, but we can
>> leave it for later as well.
>
> I think that can be a part of the main patch.
>

Okay, makes sense. Any suggestions on splitting the main patch or in
general on design/implementation is welcome.

I will rebase the patches on the latest commit. Current status is
that, I have fixed the problems reported by Jeff Janes and Mark
Kirkwood. Currently, we are doing the stress testing of the patch
using pgbench, once that is done, will post a new version. I am
hoping that it will be complete in this week.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2016-08-30 02:27:19 Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated.
Previous Message Michael Paquier 2016-08-30 02:04:31 Re: Renaming of pg_xlog and pg_clog