> You should store dates with timezone or you can't make calculations like how old is this post. I think you misread the post you responded to. It is discussi

> You should store dates with timezone or you can't make calculations like how old is this post. I think you misread the post you responded to. It is discussing the benefit of Date Vs. DateTime data types. In Postgres, by design, a date has a 1 day resolution (i.e. no concept of hours/minutes, within that date). This is hugely useful for scenarios where you intentionally want and only want a 1 day resolution. It not being timezone adjustable is a feature, not a bug. Storing a DateTime with 12:00 and then an offset of e.g. 0, is a needlessly complicated work-around when a data type that doesn't even have the concept of hours or timezones exists.