On Fri, Feb 25, 2011 at 9:40 AM, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > 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.
That's a bridge to far -- akin to saying floating point should not support equality operator. select count(*) from foo where val >= 2183.68? you are ok getting different answers depending on method of transmission of 2183.68 to the server? merlin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
