timestamp_compare ignores offset

[u-u-h]

I believe timestamp_compare should be taking the offset field into considerations, so that the same point in time in different timezones is considered 'equal' -- or is that intentional behavior? In that case I'd propose to have a second comparison function that does heed offsets.