Re: plpgsql test layout

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-11 19:55:16
Message-ID: f1b16f71-e55f-6ca1-6085-b36b69873669@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/7/17 15:21, Pavel Stehule wrote:
> 2017-12-07 20:08 GMT+01:00 Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com
> <mailto:peter(dot)eisentraut(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-12-11 20:07:20 Re: [HACKERS] Transaction control in procedures
Previous Message Tomas Vondra 2017-12-11 19:53:29 Re: [HACKERS] Custom compression methods