From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: AW: Re: GiST for 7.1 !! |
Date: | 2001-01-12 03:29:47 |
Message-ID: | Pine.BSF.4.31.0101112328460.21628-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 11 Jan 2001, Tom Lane wrote:
> Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> >> I'm unhappy again. Bad enough we accepted a new feature during beta;
> >> now we're going to expect an absolutely virgin contrib module to work
> >> everywhere in order to pass regress tests?
>
> > Last I checked, two contrib modules had to be built for regression
> > testing.
>
> Sure, but they've been there awhile. All of my concerns here are
> schedule-driven: do we really want to be wringing out a new contrib
> module, to the point where it will run everywhere, before we can
> release 7.1?
Hrmmm ... just a thought here, but how about a potential 'interactive'
regression test, where it asks if you want to run regress on GiST? If so,
do it, if not, ignore it ... ?
From | Date | Subject | |
---|---|---|---|
Next Message | Valter Mazzola | 2001-01-12 03:54:55 | Pg7.1beta3: FATAL: s_lock(0x401f7010) at spin.c:147, stuck spinlock. |
Previous Message | Lamar Owen | 2001-01-12 03:15:10 | Re: AW: Re: GiST for 7.1 !! |