Re: Re: Email to hackers for test coverage
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: "movead.li@highgo.ca" <movead.li@highgo.ca>
Cc: "ibrar.ahmad" <ibrar.ahmad@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>, Peter Geoghegan <pg@bowt.ie>, Robert Haas <robertmhaas@gmail.com>
Date: 2019-08-28T03:30:23Z
Lists: pgsql-hackers
On Tue, Aug 27, 2019 at 03:57:20PM +0800, movead.li@highgo.ca wrote: > I think your way is much better, so I change the patch and it is > 'regression_20190827.patch' now. Thanks for the new patch, I have committed the part for float4. > There are code lines related to NULL values in > ApplySortAbbrevFullComparator(), but I think the code lines for > comparing a NULL and a NOT NULL can be never reached, because it is > handled in ApplySortComparator() which is called before > ApplySortAbbrevFullComparator(). So I think it is no use to INSERT > a NULL value. But I am not sold to that part yet, for three reasons: - numeric is not a test suite designed for sorting, and hijacking it to do so it not a good approach. - it would be good to get coverage for the two extra code paths while we are on it with NULL datums. - There is no need for two INSERT queries, I am getting the same coverage with only one. Please note that I have not looked in details where we could put that, but perhaps Robert and Peter G who worked on 4ea51cd to add support for abbreviated keys have some ideas, so I am adding them in CC for input. -- Michael
Commits
-
Improve coverage of utils/float.h
- 80d0e5ba3fe0 13.0 landed
-
Adjust tuple data lookup logic in multi-insert logical decoding
- 75c1921cd6c8 13.0 cited