| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | didier <did447(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Custom Scan coverage. |
| Date: | 2019-07-03 20:48:12 |
| Message-ID: | 20190703204812.GA16622@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 I'm willing to write and propose such test suite.
We'd certainly like if there was coverage of that infrastructure.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2019-07-03 20:59:01 | Re: SQL/JSON path issues/questions |
| Previous Message | didier | 2019-07-03 20:34:52 | Custom Scan coverage. |