From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Creager <Robert(dot)Creager(at)Sun(dot)com>, PGHackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Assert failure found in 8.1RC1 |
Date: | 2005-11-04 22:08:52 |
Message-ID: | 20051104220851.GD9989@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 04, 2005 at 04:35:10PM -0500, Tom Lane wrote:
> "Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> > Could something like that be added to regression, or maybe as a seperate
> > test case for the buildfarm?
>
> If you don't have a self-contained, reproducible test case, it's a bit
> pointless to suggest adding the nonexistent test case to the regression
> suite.
Well, for things like race conditions I don't know that you can create
reproducable test cases. My point was that this bug was exposed by
databases with workloads that involved very high transaction rates. I
know in the case of my client this is due to some sub-optimal design
decisions, and I believe the other case was similar. My suggestion is
that having a test that involves a lot of row-by-row type operations
that generate a very high transaction rate would help expose these kinds
of bugs.
Of course if someone can come up with a self-contained reproducable test
case for this race condition that would be great as well. :)
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-11-04 22:20:59 | Re: Crash during elog.c... |
Previous Message | Jim C. Nasby | 2005-11-04 22:05:07 | Re: Reducing the overhead of NUMERIC data |