Re: [HACKERS] 7.4final regression failure on uw713

2003-11-26 Thread Larry Rosenman
On Tue, 25 Nov 2003, Tom Lane wrote: > [EMAIL PROTECTED] writes: > > Don't know if it's bad, but make check reports a regression failure on > > join. > > I believe we'd determined that this is an acceptable platform-specific > behavior. Yep. Due to the new qsort() in 713UP3. LER > >

Re: [HACKERS] 7.4final regression failure on uw713

2003-11-26 Thread ohp
Thansk Tom, I had vague memory about that :) Better check he? On Tue, 25 Nov 2003, Tom Lane wrote: > Date: Tue, 25 Nov 2003 19:35:07 -0500 > From: Tom Lane <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: pgsql-hackers list <[EMAIL PROTECTED]> > Subject: Re: [HACKERS]

Re: [HACKERS] 7.4final regression failure on uw713

2003-11-25 Thread Tom Lane
[EMAIL PROTECTED] writes: > Don't know if it's bad, but make check reports a regression failure on > join. I believe we'd determined that this is an acceptable platform-specific behavior. regards, tom lane ---(end of broadcast)-

[HACKERS] 7.4final regression failure on uw713

2003-11-25 Thread ohp
Hi, Don't know if it's bad, but make check reports a regression failure on join. Here's the regression.diffs *** ./expected/join.out Thu Sep 25 08:58:06 2003 --- ./results/join.out Tue Nov 25 23:46:27 2003 *** *** 1732,1739 | 6 | 6 | six | | 7 | 7 | seven |