Re:Timestamps and Time Zones in PostgreSQL (2016)
by GordonS on Sunday March 31, 2019 @07:35AM
(#19535060)
Totally agree, it's one of the reasons I came across and posted this article - I too had assumed the timestampz type stored the time zone. I'm using Postgres with Ngpsql with supports using .NET DateTimeOffset types as parameters, and as you say depending on your DB config everything can actually look as you expect in the DB...
Re:Timestamps and Time Zones in PostgreSQL (2016)
by StreamBright on Sunday March 31, 2019 @03:29AM
(#19534353)
Yep, I was wondering if you could create a postgres type that does exactly this. timestamp_utc and timestamp_local. That would make it easier to understand what is going on.
It really should have been called "TIMESTAMP IN UTC" or "NORMALIZED TIMESTAMP" or something else instead. It's especially dangerous because the results you get back from using it look correct with casual testing and you might not notice that your database is subtly wrong for a long time.