Re: Porting reports (cont'd)

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: ohp(at)pyrenet(dot)fr, Postgres Hackers List <hackers(at)postgresql(dot)org>
Subject: Re: Porting reports (cont'd)
Date: 2000-05-05 22:27:33
Message-ID: 200005052227.SAA06254@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > About Unixware 7, I sent a few reports for witch I did'nt get answer.
>
> I did see some traffic about this; not sure if it was with you or with
> Billie Allie (sp?).
>
> > There are 2 problems:
> > backend/utils/adt/int8.c doesn't compile out of the box.
> > changing around line 416 (for loop) the test i > 0 by 0 < i as previously
> > reported help things.
> > Although I haven't tried, I'm quite sur changing anything else would help
> > the same way...
>
> Compiler bugs are a PITA. But Postgres can't have inline code to
> handle all cases, esp. cases like this. "if (var op const)" is imho
> the usual style for comparisons, and obfuscating that for a single
> buggy platform isn't a Good Thing.

The bigger problem is that just fixes the comparison done by the
regression tests. Who knows how many other comparisons are broken. I
say leave it broken and don't trust it. If we fix just the
regression-shown fault, we give users a false sense of security.

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-05-05 22:33:28 Re: pg_group_name_index corrupt?
Previous Message Bruce Momjian 2000-05-05 22:24:37 Re: pg_group_name_index corrupt?