Excerpts from Merlin Moncure's message of vie feb 25 12:28:25 -0300 2011:
> no I wouldn't, and the pg_dump extra_float_digits setting addresses my
> primary concern. The client has a similar issue though -- suppose it
> fetches a value from the server and updates it back -- which record
> gets the update? You would get different results if the client was
> using binary or text features of the protocol. Not saying this is
> wrong or needs to be fixed, just pointing it out :-).
> update foo set val=val + 1 where val = 2183.68;
I think the mere idea of using floating point equality on a
WHERE clause is bogus, regardless of text or binary format.
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
In response to
pgsql-bugs by date
|Next:||From: Merlin Moncure||Date: 2011-02-25 15:48:50|
|Subject: Re: Function trunc() behaves in unexpected manner with
different data types|
|Previous:||From: Tom Lane||Date: 2011-02-25 15:39:19|
|Subject: Re: BUG #5900: Coredump on executing query |