From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: plpgsql test layout |
Date: | 2017-11-14 16:51:52 |
Message-ID: | CAFj8pRBp_9PaLRsHSq-rh-pQmW9ppZg9pxmOeioN6vx0SBHVMw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2017-11-14 17:18 GMT+01:00 Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com>:
> Something that has been bothering me for a while, while we have neatly
> organized test files for plperl, plpython, pltcl, the plpgsql tests are
> all in one giant file in the main test suite, which makes development
> and testing of plpgsql cumbersome. It is by far the largest test file
> after numeric_big now.
>
> 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
Pavel
>
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2017-11-14 16:52:05 | Re: [HACKERS] UPDATE of partition key |
Previous Message | Pavel Stehule | 2017-11-14 16:50:01 | Re: [HACKERS] SQL procedures |