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

From Kohei KaiGai
Subject Re: contrib/sepgsql regression tests are a no-go
Date
Msg-id CADyhKSUMhM_YTGCCofTYhPwkuF3og8cPqB+j-EE704QoHwB64Q@mail.gmail.com
Whole thread Raw
In response to Re: contrib/sepgsql regression tests are a no-go  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2011/9/26 Tom Lane <tgl@sss.pgh.pa.us>:
> Kohei KaiGai <kaigai@kaigai.gr.jp> writes:
>> How about this fix on regression test of sepgsql?
>
> IMO, the fundamental problem with the sepgsql regression tests is that
> they think they don't need to play by the rules that apply to every
> other PG regression test.  I don't think this patch is fixing that
> problem; it's just coercing pgxs.mk to assist in not playing by the
> rules, and adding still more undocumented complexity to the PGXS
> mechanisms in order to do so.
>
> If we have to have a nonstandard command for running the sepgsql
> regression tests, as it seems that we do, we might as well just make
> that an entirely local affair within contrib/sepgsql.
>
Are you suggesting to make a command/script to check OS environment
and run its own regression test without touching existing pg_regress
framework, even if it just utilizes existing options?
It seems to me re-inventment of a wheel....

Thanks,
--
KaiGai Kohei <kaigai@kaigai.gr.jp>


pgsql-hackers by date:

Previous
From: Kohei KaiGai
Date:
Subject: Re: [v9.2] Fix Leaky View Problem
Next
From: Fujii Masao
Date:
Subject: Re: unite recovery.conf and postgresql.conf