Re: floating point representation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pete Forman <pete(dot)forman(at)westerngeco(dot)com>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: floating point representation
Date: 2001-02-20 20:48:45
Message-ID: 6371.982702125@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pete Forman <pete(dot)forman(at)westerngeco(dot)com> writes:
> Please remind me what we are trying to do.

The real point is that we need to serve several different purposes
that aren't necessarily fully compatible.

The existing default of FLT_DIG or DBL_DIG digits seems like a good
general-purpose policy, but it doesn't meet all needs. For pg_dump,
we clearly would like to promise exact dump and restore. On the
other side, the geometry regress tests would like to suppress a few
of the noisier low-order digits. And we frequently see questions from
users about how they can display fewer digits than the system wants to
give them --- or, more generally, format the output in some special
form.

I think the idea of making a user-settable format string is a good one.
I'm just afraid of the idea of trying to shoehorn in a solution at the
last minute; if we do, we may find it's not quite right and then have
a backwards-compatibility problem with fixing it. Besides, we are in
"no new features" mode during beta. I think it should wait for 7.2.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-02-20 20:55:26 Use of LP_DELETE in buffer header
Previous Message Tom Lane 2001-02-20 20:10:47 Re: Re: beta5 ...