From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: floating point representation |
Date: | 2001-02-19 06:17:55 |
Message-ID: | 3A90BA93.5CD919A0@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > 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 ?
>
> This seems a small enough change that I do not fear fixing it at this
> late date. However, I do not like the idea of making the SET variables
> be just number of digits precision. As long as we're going to have SET
> variables, let's go for the full flexibility offered by sprintf: define
> the SET variables as the sprintf format strings to use.
Agreed.
> The defaults
> would be "%.7g" and "%.17g" (or thereabouts, not sure what number of
> digits we are currently using).
Wouldn't changing current '%.6g','%.15g'(on many platforms)
cause the regression test failure ?
> This way, someone could select the C99
> %a format if he knew that his libc supported it. Or he could force a
> particular format like %7.3f if that's what he needed in a specific
> application.
>
Regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-02-19 06:22:32 | Re: floating point representation |
Previous Message | Tom Lane | 2001-02-19 06:03:34 | Re: floating point representation |