Re: 7.3B2 initdb fails

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nic Ferrier <nferrier(at)tapsellferrier(dot)co(dot)uk>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 7.3B2 initdb fails
Date: 2002-10-04 17:54:30
Message-ID: 25091.1033754070@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Nic Ferrier <nferrier(at)tapsellferrier(dot)co(dot)uk> writes:
> DEBUG: inserting column 7 value '0'
> DEBUG: Typ != NULL
> ERROR: Bad float4 input format -- underflow

Hm. This is evidently failing this test:

static void
CheckFloat4Val(double val)
{
if (fabs(val) > FLOAT4_MAX)
elog(ERROR, "Bad float4 input format -- overflow");
if (val != 0.0 && fabs(val) < FLOAT4_MIN)
elog(ERROR, "Bad float4 input format -- underflow");
}

which is a tad surprising for an input of '0'. I think perhaps you
have a compiler bug there. Want to put a breakpoint at CheckFloat4Val
and see what's being passed in?

> I'm using Debian GNU-Linux for PPC on an iMac. 7.2 builds and
> initdb's ok.

FWIW, I've built recent sources on a PowerBook without problems,
under both LinuxPPC and OS X.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2002-10-04 18:09:10 Re: bigint and indexes
Previous Message Matthew Wakeling 2002-10-04 16:47:16 Possible bug in PostgreSQL query planner