Microsecond precision is lost when reading timetz data from Postgres.

The problem is when the postgres driver reads a TIMETZ column, it returns a java.sql.Time instance that already truncates the microsecond values, which means we aren't getting the absolute precision.

We should attempt to read TIMETZ columns in a way (likely as a string and parse locally) such that the precision isn't lost regardless whether operating in streaming or snapshot modes.