Re: plpgsql test layout - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: plpgsql test layout
Date
Msg-id CAFj8pRBp_9PaLRsHSq-rh-pQmW9ppZg9pxmOeioN6vx0SBHVMw@mail.gmail.com
Whole thread Raw
In response to plpgsql test layout  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: plpgsql test layout  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers


2017-11-14 17:18 GMT+01:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.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


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] SQL procedures
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] UPDATE of partition key