From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: floating point representation |
Date: | 2001-02-19 05:56:25 |
Message-ID: | 3A90B589.64E655D1@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
>
> > -----Original Message-----
> > From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> >
> > Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
[snip]
>
> > Peter's idea of a SET variable to control float display format might
> > not be a bad idea, but what if anything should pg_dump do with it?
> > Maybe just crank the precision up a couple digits from the current
> > defaults?
> >
>
> Currently the precision of float display format is FLT_DIG(DBL_DIG).
> It's not sufficent to distinguish float values. As Peter already suggested,
> the quickest solution would be to change XXX_DIG constants to variables
> and provide a routine to SET the variables. Strictly speaking the precision
> needed to distigush float values seems OS-dependent. It seems preferable
> to have a symbol to specify the precision.
>
The 7.1-release seems near.
May I provide the followings ?
SET FLOAT4_PRECISION TO ..
SET FLOAT8_PRECISION TO ..
Or must we postpone to fix it ?
Regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-02-19 06:03:34 | Re: floating point representation |
Previous Message | Tom Lane | 2001-02-19 05:26:44 | Re: Bug: aliasing in ORDER BY when UNIONing |