Re: "Some tests to cover hash_index"

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "Some tests to cover hash_index"
Date: 2016-08-06 04:11:37
Message-ID: CAA4eK1JxK9ddD=8Zn6npMGh9KHL-wz3wa5wE3resqsWp+W2=fA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 4, 2016 at 7:24 PM, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>
wrote:

> I am attaching the patch to improve some coverage of hash index code [1].
> I have added some basic tests, which mainly covers overflow pages. It took
> 2 sec extra time in my machine in parallel schedule.
>
>
>
>
> Hit Total Coverage
> old tests Line Coverage 780 1478 52.7
>
> Function Coverage 63 85 74.1
> improvement after tests Line Coverage 1181 1478 79.9 %
>
> Function Coverage 78 85 91.8 %
>
>

I think the code coverage improvement for hash index with these tests seems
to be quite good, however time for tests seems to be slightly on higher
side. Do anybody have better suggestion for these tests?

diff --git a/src/test/regress/sql/concurrent_hash_index.sql
b/src/test/regress/sql/concurrent_hash_index.sql
I wonder why you have included a new file for these tests, why can't be
these added to existing hash_index.sql.

+--
+-- Cause some overflow insert and splits.
+--
+CREATE TABLE con_hash_index_table (keycol INT);
+CREATE INDEX con_hash_index on con_hash_index_table USING HASH (keycol);

The relation name con_hash_index* choosen in above tests doesn't seem to be
appropriate, how about hash_split_heap* or something like that.

Register your patch in latest CF (https://commitfest.postgresql.org/10/)

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2016-08-06 04:38:47 Re: Heap WARM Tuples - Design Draft
Previous Message Bruce Momjian 2016-08-06 03:04:33 Re: Heap WARM Tuples - Design Draft