Skip site navigation (1) Skip section navigation (2)

Re: BUG #5747: TimeStamps too far into the future are invalid

From: Chris Browne <cbbrowne(at)acm(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5747: TimeStamps too far into the future are invalid
Date: 2010-11-10 22:56:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) writes:

There's an issue that JDBC doesn't cope very well with 'Infinity'
values, which is more or less the opposite of what's reported here.  I
have been tending to put "don't allow +/-Infinity" constraints onto
timestamps to avoid that particular impedance mismatch.

Just ran a little test of this with...

PostgreSQL 8.3.3, last year's JDBC, and had no difficulties pushing in
the date "2100-01-01 00:00:00".

That suggests the problem to be elsewhere.  (As, I expect, you would
(format nil "~S(at)~S" "cbbrowne" "")
Rules  of the  Evil Overlord  #194. "I  will make  several ludicrously
erroneous maps to  secret passages in my fortress  and hire travellers
to entrust them to aged hermits." <>

In response to

pgsql-bugs by date

Next:From: Jeff DavisDate: 2010-11-11 00:20:09
Subject: Re: Recovery bug
Previous:From: Tom LaneDate: 2010-11-10 18:57:27
Subject: Re: BUG #5745: geometry bug?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group