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

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

From: "Kurt Stam" <kstam(at)apache(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5747: TimeStamps too far into the future are invalid
Date: 2010-11-10 15:47:36
Message-ID: 201011101547.oAAFlaCc013378@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      5747
Logged by:          Kurt Stam
Email address:      kstam(at)apache(dot)org
PostgreSQL version: 8.3
Operating system:   OSX
Description:        TimeStamps too far into the future are invalid
Details: 

https://issues.apache.org/jira/browse/JUDDI-374

When the coverage period goes out too far postgres has issues. The coverage
periods are specified in the uddi-tck-base module in the directory
src/main/resources/uddi_data/subscription; the files
subscriptionresults3.xml and subscriptionresults4.xml:

Changing the endPoint from 2100 to 2030.

This is clearly a bug in postgres or the postgres driver. On saving no error
is thrown, however the endpoint field is set to 'invalid' which is an issue
when the date is parsed back into a timedate.

Responses

pgsql-bugs by date

Next:From: Mike FowlerDate: 2010-11-10 16:08:48
Subject: Re: BUG #5745: geometry bug?
Previous:From: Jeff MaceDate: 2010-11-10 15:13:01
Subject: BUG #5746: /etc/init.d/postgresql-9.0 status returns the wrong value

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