Hello txjmb,
Postgresql does not properly support the timestamp with time zone type according to the documentation it is just an offset timestamp. The returned column does not contain the timezone itself.
The documentation states the following:
For timestamp with time zone, the internally stored value is always in UTC (Universal Coordinated Time, traditionally known as Greenwich Mean Time, GMT). An input value that has an explicit time zone specified is converted to UTC using the appropriate offset for that time zone. If no time zone is stated in the input string, then it is assumed to be in the time zone indicated by the system’s timezone parameter, and is converted to UTC using the offset for the timezone zone.
When a timestamp with time zone value is output, it is always converted from UTC to the current timezone zone, and displayed as local time in that zone. To see the time in another time zone, either change timezone or use the AT TIME ZONE construct.
Because of the magic time conversion we do not use the timestamp with time zone type to represent ZonedDateTime in KNIME but rather varchar which doesn’t loose any information. You can also transform the zoned date time column in KNIME to UTC and then write it as timestamp into a timestamp with timezone column in Postgres as shown in the attached workflow which is based on your example workflow.
Bye
Tobias
Postgres_Timestamp_w_Timezone.knwf (19.3 KB)