| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plpgsql test layout |
| Date: | 2017-12-07 19:08:57 |
| Message-ID: | 2ea49109-c32f-3f9a-0d21-f12e5321c83b@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/14/17 11:51, Pavel Stehule wrote:
> One option would be to create a new test setup under src/pl/pgsql(/src)
> and move some of the test material from the main test suite there. Some
> of the test cases in the main test suite are more about SPI and triggers
> and such, so it makes sense to keep these in the main line. Of course
> finding the cut-off might be hard. Or maybe we'll just start with new
> stuff from now on.
>
> Any thoughts?
>
> +1
Here is a first attempt.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Start-a-separate-test-suite-for-plpgsql.patch | text/plain | 6.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-12-07 19:09:47 | Re: Speeding up pg_upgrade |
| Previous Message | Stephen Frost | 2017-12-07 19:04:24 | Re: Speeding up pg_upgrade |