Re: TimeZone issue with 42.2.1

>an not resolve type id for sun.util.calendar.ZoneInfo

This sounds like a Jackson error.

It looks like you are trying to Jackson-serialize the result of col2 column.
The column is <<time with time zone[]>>, so it is represented as PgArray
object.

As Jackson serializes PgArray, it treats whatever getter it finds as a
property.
It runs into PgArray#getResultSet and thinks it is a getter for resultSet
property. Of course that causes it to serialize underlying statement,
connection, etc.
Finally it ends up with serializing QueryExecutorImpl.timeZone field, and
it fails so.

One of the recommendations might include "avoid Jackson-serializing random
objects" =)
You might have better luck if you serialize PgArray manually or provide a
Jackson mixin annotation (see
https://github.com/FasterXML/jackson-docs/wiki/JacksonMixInAnnotations ).
Technically speaking, PgArray#getArray might be just enough.

You might ask "why did it work before 42.2.1?", and it turns out the
trigger line is
https://github.com/pgjdbc/pgjdbc/commit/a94cfeace5d66b4fe8d8fa3b16986baebaec2a11#diff-0ac94407005dd81cdbe1efa6066de013R2624

The thing is backend sends connection timezone at connection setup phase,
and pgjdbc 42.2.0 ignored that. pgjdbc 42.2.1 parses timezone message in
the initial parameter status messages, thus it ends up with non-null
timezone, thus it fails your app.

Vladimir