From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | scrappy(at)hub(dot)org (The Hermit Hacker) |
Cc: | jwieck(at)debis(dot)com, vev(at)michvhf(dot)com, maillist(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] 6.5 Release date |
Date: | 1999-06-10 14:46:11 |
Message-ID: | m10s65r-0003kGC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Marc G. Fournier wrote:
>
> On Wed, 9 Jun 1999, Jan Wieck wrote:
>
> > Sorry Mark,
> >
> > this late I have now a regression test for the NUMERIC data
> > type. Should I add it or is it too late?
>
> I personally see no problems with adding a new regression test to the
> tree...
But I see a little one on it.
The test I've created uses some values that have been
calcuated by bc(1) with a precision of 1000 digits after the
decimal point. And it excessively uses LOG, POWER etc.
The SQL script plus the expected .out are about 500K. It
run's about 1 hour and 13 minutes on a 333 MHz PII system (no
disk activity during it - real CPU time).
I think it should be somewhat separate from the usual
regression because some older hardware would need days to
complete the entire suite.
What about adding a 'make longtest' to the regression and
printing a hint about it at the end of 'make runtest'? I see
we're short of time, so I'll do it this way now and maybe
later turn the wheel back.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 1999-06-10 14:52:51 | elog(ERROR, "EvalPlanQual: t_xmin is uncommitted ?!") fixed |
Previous Message | Vadim Mikheev | 1999-06-10 14:37:13 | Re: [HACKERS] Foreign Keys |