I will stand by the fact that I cannot generate failures from
2003-02-15 (200+ runs), and I can from 2003-02-16. Just to make sure I
didn't screw up the cvs usage, I'll try again tonight if I get the
chance and re-download re-test these two days.
I can set up a script that will step through weekly dates starting from
'now' and see if the 02-16 problem might of been fixed and then
re-introduced if you like.
2003-02-16 fails 6/50 vacuum failed 1 times misc failed 3 times sanity_check failed 3 times inherit failed 1 times
triggersfailed 4 times
Cheers,
Rob
On Mon, 28 Jul 2003 02:14:32 -0400
Tom Lane <tgl@sss.pgh.pa.us> said something like:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I have only been running nightly paralell regression runs since June
> > 27, so it is possible that the paralell regression was broken in
> > February, fixed in May, then broken some time after that.
>
> Any further progress on this?
>
> My best theory at the moment is that we have a problem with relcache
> entry creation failing if it's interrupted by an SI inval message at
> just the right time. I don't much want to grovel through six months
> worth of changelog entries looking for candidate mistakes, though.
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 3: if posting/reading
> through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that
> your message can get through to the mailing list cleanly
>
>
-- 06:57:40 up 10 days, 10:57, 2 users, load average: 2.17, 2.08, 1.83
