From: | James David Smith <james(dot)david(dot)smith(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Don't understand error? |
Date: | 2014-04-15 22:28:55 |
Message-ID: | CAMu32ACZ--KMWzJjipW2XF9vP2+a2VvDN2LSPNrMhFS9B2Puhg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Just to say thanks. It looks like the error originated from multiplying the
result of an EXTRACT(EPOCH from time) . Once I added ::numeric to this, the
query ran ok. I also changed a couple of integer types to numeric, so it
might have been those either.
On 14 Apr 2014 15:25, "James David Smith" <james(dot)david(dot)smith(at)gmail(dot)com>
wrote:
> Good tip. Thanks. I don't think there are many values stored like
> that, so it should make it a bit easier to find.
>
> On 14 April 2014 15:24, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > James David Smith <james(dot)david(dot)smith(at)gmail(dot)com> writes:
> >> Yes, I thought the same. Glad to know that I might be along the right
> >> lines. I've started taking parameters out one-by-one to try and find
> >> the culprit. Yes, there are a variety of numbers stored as NUMERIC in
> >> various places. For example:
> >
> > AFAIR, there is no such thing as an underflow error in the type-NUMERIC
> > code --- it will happily round to zero instead. You should be looking
> for
> > something involving float4 or float8 (aka real/double precision).
> >
> > regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Anderson Amaral | 2014-04-16 13:17:31 | Running psql queries on Excel without Power Query |
Previous Message | Alan Hodgson | 2014-04-14 21:23:09 | Re: Images stored in bytea datatype |