On 2019-Jul-03, didier wrote:
> Currently there's 0 coverage of CustomScan code path in core.
Yeah :-(
> What about adding a noops custom_scan test in src/test/modules/ ? Or
> is it out of pg perimeter and each extension using it should take are
> of themselves?
>
> If there's an interest
Hi,
Currently there's 0 coverage of CustomScan code path in core.
What about adding a noops custom_scan test in src/test/modules/ ? Or
is it out of pg perimeter and each extension using it should take are
of themselves?
If there's an interest I'm willing to write and propose such test suite.
