| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Write Ahead Logging for Hash Indexes |
| Date: | 2016-09-07 10:08:21 |
| Message-ID: | CAA4eK1+pK0xOPAi=kgokXN51AYN-FaryCw0Pb410v=75eqxhPQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 7, 2016 at 3:28 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> Okay, I have fixed this issue as explained above. Apart from that, I
> have fixed another issue reported by Mark Kirkwood upthread and few
> other issues found during internal testing by Ashutosh Sharma.
>
Forgot to mention that you need to apply the latest concurrent hash
index patch [1] before applying this patch.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kuntal Ghosh | 2016-09-07 10:22:47 | Re: WAL consistency check facility |
| Previous Message | Amit Kapila | 2016-09-07 09:58:34 | Re: Write Ahead Logging for Hash Indexes |