Oliver Jowett <oliver@opencloud.com> writes:
> While testing this patch I noticed we have existing date-related
> regression failures (not related to the patch) against 7.2.x:
>> [junit] Testcase: testSetTimestampWTZ(org.postgresql.test.jdbc2.TimestampTest): Caused an ERROR
>> [junit] ERROR: Bad timestamp external representation '2000-02-08 04:00:00.120000+1300'
I believe this is a server bug, not JDBC's fault. The timestamp code
rejected +1300 as an invalid timezone until not too long ago. It is
valid though...
regards, tom lane