From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | ohp(at)pyrenet(dot)fr, Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: cvs head initdb hangs on unixware |
Date: | 2008-12-10 17:29:36 |
Message-ID: | 3673.1228930176@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> ohp(at)pyrenet(dot)fr wrote:
>> Never saw a problem with gcc, hp-ux, darwin or M$?
> Sure, that's not what I was saying. My point is, when there's a bug in
> one version of a compiler, we shouldn't try to adapt PostgreSQL to that
> bug. Instead, we should narrow down the bug, get it fixed in the
> compiler, and tell users to use the most recent version of the compiler
> where the bug has been fixed.
We should certainly file a bug report against the compiler. However,
ISTM a workaround is a good idea too if it's not too ugly (which this
one isn't). If a bug exists in one compiler there might be similar
bugs in other compilers.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-12-10 17:36:38 | Re: cvs head initdb hangs on unixware |
Previous Message | Zdenek Kotala | 2008-12-10 17:27:05 | Re: cvs head initdb hangs on unixware |