Nov. 10, 2016
11:25 p.m.
On Nov 10, 2016, at 3:17 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
FWIW, I beg to differ on that. I know this will break Postgres, which is doing pretty much the same thing as Emacs, ie relying on a lot of calls to localtime() to infer the system's active timezone. We only do that once during database initialization, so we're not badly exposed, but nonetheless this is another data point suggesting that programs in the field do have this assumption.
So I shouldn't run Postgres on any Mac that I can conveniently carry while it's running, because if I carry the Mac into a car, train, airplane, or boat, the system's active time zone might change out from under Postgres. :-) Why does Postgres need to know the system's active time zone?