RE: [HACKERS] ERROR: Unable to identify an operator '=' for types 'numeric' and 'float8'

Hiroshi Inoue <inoue@tpf.co.jp>

From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Tom Lane" <tgl@sss.pgh.pa.us>, "Thomas Lockhart" <lockhart@alumni.caltech.edu>
Cc: "Michael Meskes" <meskes@postgreSQL.org>, "PostgreSQL Hacker" <pgsql-hackers@postgreSQL.org>
Date: 2000-02-17T02:37:23Z
Lists: pgsql-hackers
> -----Original Message-----
> From: owner-pgsql-hackers@postgreSQL.org
> [mailto:owner-pgsql-hackers@postgreSQL.org]On Behalf Of Tom Lane
>
> Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
> > One hesitation I have is the performance hit in mixing FLOAT and
> > NUMERIC; I (probably) don't want to make NUMERIC the "best" numeric
> > type, since it is potentially so slow.
>
> I concur --- I'd be inclined to leave FLOAT8 as the top of the
> hierarchy.  But NUMERIC could be stuck in there between int and float,
> no?  (int-vs-numeric ops certainly must be promoted to numeric...)
>

Is this topic related to the fact that 1.1 is an FLOAT8 constant in
PostgreSQL ?
I've not understood at all why it's OK.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp