Re: contrib/sepgsql regression tests are a no-go - Mailing list pgsql-hackers

From Robert Haas
Subject Re: contrib/sepgsql regression tests are a no-go
Date
Msg-id CA+TgmoYQQ0=ionn07-AGDGve_LtzUm0_PfsPp3r-dVinsyyFTg@mail.gmail.com
Whole thread Raw
In response to contrib/sepgsql regression tests are a no-go  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: contrib/sepgsql regression tests are a no-go
Re: contrib/sepgsql regression tests are a no-go
List pgsql-hackers
On Sun, Sep 25, 2011 at 9:07 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> As a stopgap, what about removing sepgsql from the list of contrib
> modules tested by "make -C contrib check"?

+1.

In fact, I've been wondering if we ought to go a step further and not
recurse into the sepgsql directory for *any* of the targets.  Then we
could get rid of the associated configure option, which no longer
serves any other purpose, and just say that if you want to build (or
regression-test) sepgsql, well, you gotta go to that directory and do
it by hand.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Inlining comparators as a performance optimisation
Next
From: Tom Lane
Date:
Subject: Re: contrib/sepgsql regression tests are a no-go