Re: BUG #16027: Invalid output of to_timestamp

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeffrey Sturm <Jeff(dot)Sturm(at)HelloWorld(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16027: Invalid output of to_timestamp
Date: 2019-09-26 16:31:43
Message-ID: 17811.1569515503@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jeffrey Sturm <Jeff(dot)Sturm(at)HelloWorld(dot)com> writes:
> The problem actually manifests within the JDBC driver:
> org.postgresql.util.PSQLException: Bad value for type timestamp/date/time: {1}
> If what you are saying is that -05:32:11 is a perfectly valid offset from UTC, then this is a JDBC driver issue rather than pgsql, and if this is not the right bug list for JDBC reports I can take it there.

Well, it's a valid offset so far as Postgres is concerned. Some poking
around suggests that relevant standards such as ISO 8601 only admit UTC
offsets specified to the nearest minute --- but tzdb has some entries
specified to seconds, so that's what we follow.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Verite 2019-09-26 16:39:40 Re: BUG #16020: ICU Collations querys
Previous Message Peter Eisentraut 2019-09-26 16:28:39 Re: BUG #16020: ICU Collations querys