From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "Some tests to cover hash_index" |
Date: | 2016-08-24 16:48:19 |
Message-ID: | CA+Tgmoa2Vzvg2s3HKX1exSp=wndoX2uGK=Jx5ghyp7+EZ+Ah7w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Aug 24, 2016 at 2:34 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Wed, Aug 24, 2016 at 11:38 AM, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> wrote:
>>> Well, that change should be part of Amit's patch to add WAL logging,
>>> not this patch, whose mission is just to improve test coverage.
>>
>> I have just removed the warning message from expected output file as i
>> have performed the testing on Amit's latest patch that removes this
>> warning message from the hash index code.
>>
>
> I think you are missing what Robert wants to point out. You don't
> need to remove the warning message when you are adding new test cases
> on top of Mithun's patch even if those new tests helps to cover the
> code path which is required for wal-hash-index patch.
Right. The point is, if somebody applies this patch on top of master,
the regression tests will now fail because of that missing line. That
means nobody is going to commit this.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2016-08-24 17:02:28 | Re: Write Ahead Logging for Hash Indexes |
Previous Message | Anastasia Lubennikova | 2016-08-24 16:41:46 | Re: Optimization for lazy_scan_heap |