From: | Colin Taylor <colin(dot)taylor(at)gmail(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: date/time out of range |
Date: | 2011-01-18 20:36:35 |
Message-ID: | AANLkTimnzqp0y2HsUo3URvGbtNoZA8gGzenxRkpeZDSv@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Oops I'm an idiot of course this is server side only.
For more background I'm running a java log processing system using
straight JDBC, I will get logs error out occasionally with this error
and then rerun them and its all good! As the process is multi-threaded
runs aren't idempotent but this particular query would always occur.
I cant reproduce this problem on redhat only OSX so its good that I
dont get in production only on my dev box..
On Wed, Jan 19, 2011 at 5:10 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Samuel Gendler <sgendler(at)ideasculptor(dot)com> writes:
>>> On 18/01/11 17:00, Colin Taylor wrote:
>>>> 10127 Caused by: org.postgresql.util.PSQLException: ERROR: date/time
>>>> field value out of range: "2011-01-12 21:30:00.000000 +13:00:00"
>
>> Is there a +13:00:00 timezone or does that wind up crossing the date line?
>> If Java has no mechanism for converting that time zone to whatever date/time
>> type it is trying to convert to, the exception would make sense.
>
> The weird thing is that the message appears to be a server-side error;
> at least it exactly matches the spelling of one server error. But I
> don't understand how come it occurs only from JDBC and not in psql.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2011-01-18 21:31:57 | Re: jdbc spec violation for autocommit=true & addbatch/executeBatch |
Previous Message | Quartz | 2011-01-18 19:50:45 | Re: jdbc spec violation for autocommit=true & addbatch/executeBatch |