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

From: "Gene Sokolov" <hook(at)aktrad(dot)ru>
To: "PostgreSQL Hacker" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] ERROR: Unable to identify an operator '=' for types 'numeric' and 'float8'
Date: 2000-02-16 16:00:05
Message-ID: 080b01bf7896$e6e184b0$0d8cdac3@aktrad.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)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...)

If you cast NUMERIC to FLOAT8, then you would loose precision and it would
be counterintuitive type promotion (at least for a C programmer). If someone
wants speed over correctness, he can always explicitly cast NUMERIC to
FLOAT8. Seems like "correct" should take precedence over "fast", at least as
long as there is a way to do "fast".

Gene Sokolov.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-02-16 16:03:29 Re: [HACKERS] parser changes
Previous Message Lamar Owen 2000-02-16 15:57:03 Re: [HACKERS] Postgres meets InterBase (ZDNet)