On Fri, Sep 16, 2016 at 11:22 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> I do want to work on it, but it is always possible that due to some
> other work this might get delayed. Also, I think there is always a
> chance that while doing that work, we face some problem due to which
> we might not be able to use that optimization. So I will go with your
> suggestion of removing hashscan.c and it's usage for now and then if
> required we will pull it back. If nobody else thinks otherwise, I
> will update this in next patch version.
>
In the attached patch, I have removed the support of hashscans. I
think it might improve performance by few percentage (especially for
single row fetch transactions) as we have registration and destroy of
hashscans.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com