Found the stuff below. Maybe there is more information in the new release itself. I'll post anything else I find...
"...We also saw a few changes to time oriented data handling, some of which was related to some recent discussions on the -general list. Now when a TIMESTAMP, TIME, or INTERVAL precision is specified larger than our
implementation limits, a NOTICE is issued and we use the max supported value. Previously this would have resorted in an error, but the change was needed to allow easy porting from pre-7.3 releases where the limits were higher. We also now allow 60 seconds fields of TIMESTAMP, TIME, or INTERVAL input values. This is actually appropriate for spec compliance and will also help in porting from older pg_dump files."
"Tom Lane added in some code to add code
to test for unknown timezone names (following some ideas from Ross Reedstrom a couple months back) and to detect timezones that are using leap-second timekeeping. Along with this he also made DecodePosixTimezone() a tad more robust. Tom also finished removing the support for autocommit from the back end based on recent discussions,
though there is still a need to support this on the client side in lippq."