Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
> ... I don't really care whether what we currently have is
> "timestamp" or "timestamp with time zone", but if, for example, I/we
> implement an SQL9x-conforming "timestamp with time zone" it will not get
> used.
Okay, if we believe those two facts, then calling our existing timestamp
type "timestamp with time zone" does not make us more standards
conformant, it only makes us more verbose. I'd prefer to use the
shorter name for the datatype we believe is actually useful ...
regards, tom lane