From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Robins Tharakan <tharakan(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Brazil disables DST - 2019b update |
Date: | 2019-07-12 14:33:30 |
Message-ID: | 27802.1562942010@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Fri, Jul 12, 2019 at 4:14 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The usual recommendation on well-maintained production systems is to
>> configure PG with --with-system-tzdata, then rely on your platform
>> vendor for timely updates of that data.
> It should be noted that this is not true on Windows -- on Windows we cannot
> use the system timezone functionality, and rely entirely on the files we
> ship as part of our release.
IMO this is one of many reasons why Windows isn't a great choice of
platform for production use of Postgres ;-).
I hear that Microsoft is going to start embedding some flavor of
Linux in Windows, which presumably would extend to having a copy of
/usr/share/zoneinfo somewhere. It'll be interesting to see how that
works and whether they'll maintain it well enough that it'd be a
plausible tzdata reference.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2019-07-12 15:08:32 | Re: Brazil disables DST - 2019b update |
Previous Message | Magnus Hagander | 2019-07-12 14:22:58 | Re: Brazil disables DST - 2019b update |