Along the lines of this related question:

Are there any valid use cases for actually using TIME WITH TIME ZONE or should it be considered an anti-pattern?

To be clear: I am asking about TIME…, not TIMESTAMP….


1 Answer 1


There is no valid use case. time with time zone is broken by design and only included in Postgres since it's in the SQL standard. Don't use it.

Time zones can have daylight saving time (DST) rules, which do not work with timetz at all.

In fact, the use of time with time zone is officially discouraged:

The type time with time zone is defined by the SQL standard, but the definition exhibits properties which lead to questionable usefulness. In most cases, a combination of date, time, timestamp without time zone, and timestamp with time zone should provide a complete range of date/time functionality required by any application.

  • Yea, I was going answer along the same lines I wanted to show it was broken by design but it was remarkably hard to demonstrate it. Oct 1, 2017 at 0:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.