New answers tagged timezone
Yes, plenty of drawbacks, because it's wrong. imagine if this server depended on having accurate timestamps, particularly if communicating with client systems a la Kerberos. You should be setting servers to use UTC and also telling them what time zone they're in. OS dependent, of course.
Ideally, all of your gear (servers, networking, etc.) should use UTC time. This does away with any possible ambiguity due to time zones, daylight saving time, etc. If that's not possible, then the next best option is to have everything on the same time zone, as you've proposed. There is nothing "wrong" with this per se, as long as each system is ...
The default value for the TimeZone setting has changed on release 9.2: 9.1 TimeZone: (..) If not explicitly set, the server initializes this variable to the time zone specified by its system environment. (...) 9.2 TimeZone: (...) The built-in default is GMT, but that is typically overridden in postgresql.conf; initdb will install a setting ...
Top 50 recent answers are included