| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: contrib/sepgsql regression tests are a no-go |
| Date: | 2011-09-26 03:49:46 |
| Message-ID: | CA+TgmoYQQ0=ionn07-AGDGve_LtzUm0_PfsPp3r-dVinsyyFTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Sep 25, 2011 at 9:07 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-09-26 04:06:38 | Re: contrib/sepgsql regression tests are a no-go |
| Previous Message | Robert Haas | 2011-09-26 03:46:29 | Re: Inlining comparators as a performance optimisation |