| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, The Hermit Hacker <scrappy(at)hub(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: AW: Re: GiST for 7.1 !! |
| Date: | 2001-01-12 15:02:56 |
| Message-ID: | 15632.979311776@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
> What's wrong with
> warning message if GiST test not passed ?
You're being *way* too optimistic. An output discrepancy in a test of
GIST we could live with. But think about other scenarios:
1. GIST test coredumps on some platforms. This corrupts other tests
(at least through the "system is starting up" failure mode), thus
masking problems that we actually care about.
2. GIST test code does not compile on some platforms, causing "make check"
to fail completely.
At this point my vote is to leave the GIST test in contrib for 7.1.
Anyone who actually cares about GIST (to be blunt: all three of you)
can run it as a separate step. I don't want it in the standard regress
tests until 7.2, when we will have a reasonable amount of time to test
and debug the test.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-01-12 15:10:38 | Re: AW: Re: GiST for 7.1 !! |
| Previous Message | Thomas Lockhart | 2001-01-12 14:54:57 | Re: AW: Re: tinterval - operator problems on AIX |