Re: out of range error while restore using pgdump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Samir Magar <samirmagar8(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org, Swapnil Vaze <swapvaze28(at)gmail(dot)com>
Subject: Re: out of range error while restore using pgdump
Date: 2017-01-16 15:30:40
Message-ID: 7680.1484580640@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Samir Magar <samirmagar8(at)gmail(dot)com> writes:
> pg_restore: [archiver (db)] COPY failed for table "tcb_test": ERROR:
> "5.40593839802118076e-315" is out of range for type double precision

That's ... weird. I don't have RHEL7 installed to test, but I don't
see any error for that value on RHEL6 or Fedora 25, which ought to
bracket that version.

I suppose your version of strtod() must be refusing to do gradual
underflow, or else you're running on hardware that doesn't do
IEEE-compliant arithmetic. But I didn't think RHEL supported any
such hardware (unless maybe it's s/390?). And I can't find any
documentation suggesting that glibc supports turning off gradual
underflow, either.

Perhaps you're using some extension that fools around with the
hardware floating-point options?

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Karl Czajkowski 2017-01-18 22:36:33 optimizing immutable vs. stable function calls?
Previous Message Samir Magar 2017-01-16 09:20:30 out of range error while restore using pgdump