Re: [COMMITTERS] pgsql: Bloom index contrib module - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Bloom index contrib module
Date
Msg-id 5835.1460254081@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Bloom index contrib module  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Bloom index contrib module  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
I wrote:
> I was depressed, though not entirely surprised, to find that you get
> exactly that same line-count coverage if the table size is cut back
> to ONE row.

Oh, I found the flaw in my testing: there are two INSERTs in the test
script and I was changing only one of them.  After correcting that,
the results behave a little more sanely:
              Line Coverage           Functions
1 row:         70.4 %    349 / 496    93.1 %    27 / 29
10 row:        73.6 %    365 / 496    93.1 %    27 / 29
100 rows:      73.6 %    365 / 496    93.1 %    27 / 29
1000 rows:     75.4 %    374 / 496    93.1 %    27 / 29

Still, we've reached the most coverage this test can give us at 1000
rows, which still means it's wasting the last 99% of its runtime.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Bloom index contrib module
Next
From: David Rowley
Date:
Subject: Re: Performance improvement for joins where outer side is unique