X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 18D7CD1D8C8 for ; Mon, 12 Jan 2004 15:39:50 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 82836-10 for ; Mon, 12 Jan 2004 11:39:23 -0400 (AST) Received: from smtp102.mail.sc5.yahoo.com (smtp102.mail.sc5.yahoo.com [216.136.174.140]) by svr1.postgresql.org (Postfix) with SMTP id B6F34D1DA2C for ; Mon, 12 Jan 2004 11:39:18 -0400 (AST) Received: from unknown (HELO europa.janwieck.net) (janwieck@68.80.245.191 with login) by smtp102.mail.sc5.yahoo.com with SMTP; 12 Jan 2004 15:39:22 -0000 Received: from Yahoo.com (ismtp.afilias.com [216.217.55.254]) (authenticated) by europa.janwieck.net (8.11.6/8.11.6) with ESMTP id i0CFdrk26341; Mon, 12 Jan 2004 10:39:53 -0500 Message-ID: <4002B153.7030705@Yahoo.com> Date: Mon, 12 Jan 2004 09:38:11 -0500 From: Jan Wieck User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Glaesemann Cc: Bruce Momjian , pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org, aspire420@hotpop.com Subject: Re: [HACKERS] IEEE 754 References: <200401050051.i050pDF22348@candle.pha.pa.us> <8C33EA12-3F44-11D8-BA4F-000A95C88220@myrealbox.com> In-Reply-To: <8C33EA12-3F44-11D8-BA4F-000A95C88220@myrealbox.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/138 X-Sequence-Number: 12001 Michael Glaesemann wrote: > On Jan 4, 2004, at 6:51 PM, Bruce Momjian wrote: > >> Michael Glaesemann wrote: >>> >>> On Dec 29, 2003, at 11:28 AM, Sai Hertz And Control Systems wrote: >>>> I would like to share my concerns about the IEEE 754 specification >>>> and >>>> floating point handling by PostgreSQL . >>> >>> What specifically are your concerns regarding floating point handling >>> and PostgreSQL? I'm not in a position to address your concerns, but I >>> would like to know what they are. >> >> Floating point math itself is not precise, but rather an approximation, >> usually of 8 or 14 digits. You can't approximate money. This isn't a >> PostgreSQL issue but rather a general programming issue. > > Thanks, Bruce. I assume the arbitrary precision arithmetic Jan > mentioned which is used for the NUMERIC type takes care of this. That was the whole intention. Although Bruce is wrong, since most of the time money is approximated. It is only in "bookkeeping" where this is not allowed. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #