Vladimir Sitnikov

I think this is the same as https://bugs.openjdk.org/browse/JDK-8255148 In other words, the exception is probably an information-only, and it does not mean any error condition. I am leaning towards closing...

I do not think we close it twice though.

> doSomething(optional.orElseGet(() -> fail("should not be called"))); It should better be `doSomething(optional.orElseThrow(() -> fail("should not be called")));` to better convey the intention > Stream.of().map(entry -> fail("should not be called")); Is...

The issue with `ZonedDateTime` is that its `ZoneId` might have several variations: * `ZoneOffset`. In that case, it is pretty much the same thing as `OffsetDateTime`, so we can support...

There are multiple demands mixed in the issue, so I decided to give it a try and implemented `Instant` for `timestamptz` and `timetz`. See #3734 > marschall: I am against...

A caveat with `ZonedDateTime` is it has neither `MIN` nor `MAX` constants, so it is not clear how to map from `+-infinity` to `ZonedDateTime`. The reason for missing `MIN/MAX` is...

> "Dear database, I handle time zones on the app side. You do not have to worry about it at all" >Which I think is a super legit approach :)...

I've added `ZonedDateTime` support as well with errors on `infinity`/`-infinity`

>Is providing support for (getting) OffsetDateTime and ZonedDateTime by always interpreting as UTC really valuable? 1) `OffsetDateTime` has been implemented in https://github.com/pgjdbc/pgjdbc/pull/2467, and I believe it is way better that...

@davecramer , do you mean back-port build scripts to all the past releases? It might take time. I wonder if we can re-release with Java 8 instead.