PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID16060
PG Version12.0
OSUbuntu
Opened2019-10-15 18:52:12+00
Reported byJan Marencik
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      16060
Logged by:          Jan Marencik
Email address:      (redacted)
PostgreSQL version: 12.0
Operating system:   Ubuntu
Description:        

postgresql 42.2.8

Java DateOffsetTime value correctly stored to database to timestamptz. I see
right conversion to string including right time zone.
Opposite process doesn't get the right DateOffsetTime value from database.
In my case the string representation stored to database is 2019-10-15
20:26:41.391055+02 but I get 2019-10-15T18:26:41.391055Z which doesn't by +2
hours which is my time zone.
I think the bug is in TimestampUtils line 513:
    // Postgres is always UTC
    OffsetDateTime result = OffsetDateTime.of(ts.year, ts.month, ts.day,
ts.hour, ts.minute, ts.second, ts.nanos, zoneOffset)
        .withOffsetSameInstant(ZoneOffset.UTC);
The last line ".withOffsetSameInstant(ZoneOffset.UTC);" is the bug

Messages

DateAuthorSubject
2019-10-15 18:52:12+00PG Bug reporting formBUG #16060: JDBC - badly gets DateOffsetTime value from database
2019-10-16 04:20:27+00Michael PaquierRe: BUG #16060: JDBC - badly gets DateOffsetTime value from database
2019-10-16 05:35:27+00Dave CramerRe: BUG #16060: JDBC - badly gets DateOffsetTime value from database
2019-10-16 10:52:30+00stan(at)marencik(dot)czRe: BUG #16060: JDBC - badly gets DateOffsetTime value from database