2 ms·
What does this break? I always want either UTC or the user's timezone (that is, the person using the interface, so that "your meeting next week at 13:00 in Eur
by arp242 3y ago
What does this break?
I always want either UTC or the user's timezone (that is, the person using the interface, so that "your meeting next week at 13:00 in Europe/Amsterdam TZ" is accurate).
I don't think I ever want the database's timezone. I never care about it, so just setting to UTC always seemed to work for me?
- marcosdumay 3y agoFor a start, your cron jobs will be scheduled at UTC, what will induce people into many mistakes.
- arp242 3y agoYou can set timezone = 'UTC' in your postgresql.conf, don't need to change it for the entire system. And personally I wouldn't really consider that "breaking", that seems far too strong. Although it can obviously a caveat. (Personally I do prefer to set the system time to UTC though, so it doesn't matter if the server is in Singapore, Germany, or the US – it's always the same. Also makes migrating things to different machines or moving VPSes to a different data centre a lot easier.)
- hot_gril 3y agoIt's good to set all servers to UTC. EC2 does this by default, so do most cloud Postgres instances.