bad_time = datetime.datetime(2025, 4, 14, 14, 0, 0)
As a rule of thumb: It preserves the global truth of when an event happened. Use TIMESTAMP only when the "wall clock" time is more important than the physical moment in time. By adhering to this hierarchy, developers can avoid the "time-traveling" bugs that plague global applications and ensure their data remains a reliable record of history. postgres timestamp vs timestamptz
Think of this as a "naive" timestamp. It represents a specific time on the clock, completely agnostic of where on Earth you are. bad_time = datetime