From: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Rahila Syed <rahilasyed(dot)90(at)gmail(dot)com>, Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com> |
Subject: | Re: Parallel Index Scans |
Date: | 2016-12-22 08:05:37 |
Message-ID: | 1d6353a0-63cb-65d9-a70c-0913899d5b06@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/22/2016 09:49 AM, Amit Kapila wrote:
> I think you can focus on the handling of array scan keys for testing.
> In general, one of my colleagues has shown interest in testing this
> patch and I think he has tested as well but never posted his findings.
> I will request him to share his findings and what kind of tests he has
> done, if any.
Sure, We (Prabhat and I) have done some testing for this feature
internally but never published the test-scripts on this forum. PFA the
sql scripts ( along with the expected .out files) we have used for
testing for your ready reference.
In addition we had generated the LCOV (code coverage) report and
compared the files which are changed for the "Parallel index scan" patch.
You can see the numbers for "with patch" V/s "Without patch" (.pdf
file is attached)
--
regards,tushar
Attachment | Content-Type | Size |
---|---|---|
pis_testcases.sql | text/x-sql | 22.4 KB |
pis_testcases.out | text/plain | 72.7 KB |
lcov_report_compare.pdf | application/pdf | 50.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2016-12-22 08:35:51 | Re: Declarative partitioning - another take |
Previous Message | Fabien COELHO | 2016-12-22 07:39:52 | Re: BUG: pg_stat_statements query normalization issues with combined queries |