Imho the behavior of timestamp code is somewhat awkward
for dates that do not fit into a time_t (>2038 or < 1901).
Times in the time_t range are displayed in local time including DST.
Times outside that range are displayed in UTC. I would have expected
UTC plus local offset not taking DST into account.
When setting datestyle to ISO I get a timezone offset, even when SQL99
says timezone is only available if the column was defined as
"timestamp with timezone". Dealing with the stupid mktime issue
I think the standard intended to not involve any issues with
timezones or DST for the timestamp datatype.
The timestamp implementation is not SQL99 conformant.
Andreas