Re: plpgsql test layout - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: plpgsql test layout
Date
Msg-id f1b16f71-e55f-6ca1-6085-b36b69873669@2ndquadrant.com
Whole thread Raw
In response to Re: plpgsql test layout  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: plpgsql test layout  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 12/7/17 15:21, Pavel Stehule wrote:
> 2017-12-07 20:08 GMT+01:00 Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com
> <mailto:peter.eisentraut@2ndquadrant.com>>:
> 
>     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.
> 
> 
> looks ok

Any other thoughts on this?  If not, I'd like to commit it, give the
buildfarm a run at it (looking at the client code, it should be fine),
and then rebase some ongoing work on top of it.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] Custom compression methods
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Transaction control in procedures