Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id UAA58390 for ; Sat, 15 Jan 2000 20:07:39 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id UAA17160 for ; Sat, 15 Jan 2000 20:07:37 -0500 (EST) To: pgsql-sql@postgreSQL.org Subject: Patches for various NUMERIC bugs posted on pgsql-patches Date: Sat, 15 Jan 2000 20:07:37 -0500 Message-ID: <17157.947984857@sss.pgh.pa.us> From: Tom Lane I dug into the various reports of NUMERIC/DECIMAL bugs today, and found that there were several different bugs lurking there. If you are interested in having fixes to these problems before 7.0 comes out, see the patches I posted on the pgsql-patches list. Problems fixed: * Platform-dependent failure of NUMERIC AVG() function. * Bogus rounding/overflow check would cause zero to be rejected in a field that has only fraction digits, e.g. DECIMAL(4,4). * numeric_out's rounding code could actually cause a coredump in pathological cases (hasn't been reported from the field, though). * NUMERIC basically didn't work at all in PL/PGSQL functions; on most platforms you'd get bogus "overflow" errors. regards, tom lane