X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 4FBF230EE16; Mon, 16 Jun 2003 23:36:11 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 51232-04; Mon, 16 Jun 2003 20:36:00 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 6808130EF3C; Mon, 16 Jun 2003 20:35:59 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h5GNZxE26867; Mon, 16 Jun 2003 19:35:59 -0400 (EDT) From: Bruce Momjian Message-Id: <200306162335.h5GNZxE26867@candle.pha.pa.us> Subject: Re: [HACKERS] Our FLOAT(p) precision does not conform to spec In-Reply-To: <7114.1055801746@sss.pgh.pa.us> To: Tom Lane Date: Mon, 16 Jun 2003 19:35:59 -0400 (EDT) Cc: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200306/163 X-Sequence-Number: 13921 Tom Lane wrote: > Is it worth trying to provide some sort of backwards-compatibility mode? > We could imagine adding a GUC variable to select binary or decimal > precision, but I really don't want to. It would increase the amount of > work needed by more than an order of magnitude, and this problem doesn't > seem worth it. I'd rather just list this under Incompatibilities in the > 7.4 release notes. Let's just change it and list it in the release notes as an incompatibility --- anything else is too confusing. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073