Re: floating point representationu

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: floating point representationu
Date: 2001-02-20 02:02:17
Message-ID: 200102200202.VAA18756@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> Tom Lane wrote:
> >
> > Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > > Actually, you're going to have to recode the float*in() functions, using
> > > scanf, and scanf's formats are not always equivalent to printf's.
> >
> > Further thought: one answer to this is to institute four SET variables,
> > two for output and two for input; perhaps FLOAT8_FORMAT, FLOAT8_IN_FORMAT,
> > and similarly for FLOAT4. The input formats would normally just be
> > "%lg" and "%g" but could be changed for special cases (like reading
> > table dumps prepared with %a output format).
> >
>
> >From the first I don't want to change the current default
> output format
> "%." #FLT_DIG "g" (REAL)
> "%." #DBL_DIG "g" (DOUBLE PRECISION)
> for 7.1 because their changes would cause a regress
> test failure.

But we run regress with the proper setting, right? How does giving
people the ability to change the defaults affect the regression tests?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-02-20 02:30:14 Re: Turkish locale bug
Previous Message Hiroshi Inoue 2001-02-20 01:41:52 Re: floating point representation