News for hackers. Stuff that matters.
Re:PostgreSQL Timestamps and Timezones: What You Need to Kno... by paulryanrogers on Sunday February 13, 2022 @08:59PM (#30327628)
>The only way to future-proof your code so that it will continue to give currently correct results no matter what rule changes are made is always to persist data as timestamptz values and to let the system—kept current with the tz database—work its magic according to the rules that it presently embodies.

Key take away IMO

Re:PostgreSQL Timestamps and Timezones: What You Need to Kno... by taylodl on Wednesday February 16, 2022 @03:21PM (#30365174)
Yep. That's what I do. Preserves your sanity and allows you to order events across timezones and time changes.