| From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Regarding timezone |
| Date: | 2014-09-17 20:14:05 |
| Message-ID: | CALSLE1P+Wof9ek7BjOkmLiLFGZ-jqJY7Mv8eBBowz2Sj+9ac=Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Sep 18, 2014 at 1:22 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 09/17/2014 12:26 PM, Dev Kumkar wrote:
>
>> I hope the binaries archive containing ""pgsql/share/postgresql/
>> timezone/Europe/Moscow" uploaded at
>> http://www.enterprisedb.com/products-services-training/pgbindownload
>> will also get corrected.
>>
>
> They will.
>
Thanks, on 25 October 2014 the timezone will change permanently. Currently
binaries are at 9.3.5.1 level, will keep an watch on the update.
No, because a timezone(versus an offset) definition includes a historical
> record of the changes in the timezone. For all the gory details see:
>
> http://en.wikipedia.org/wiki/Tz_database
Great info! So the historical Moscow timestamps will still reflect GMT+4
based on the datetime.
Sure, awaiting fix and will cross-check the behavior.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dev Kumkar | 2014-09-17 20:36:46 | Re: [SQL] pg_multixact issues |
| Previous Message | Adrian Klaver | 2014-09-17 19:52:23 | Re: Regarding timezone |