| From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Regarding timezone |
| Date: | 2014-09-17 19:26:47 |
| Message-ID: | CALSLE1NYXxkpUN7_t7H7C1pg6pm4cpjQHbva2msEtMv-U_2Lww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Sep 18, 2014 at 12:01 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The next set of minor releases, whenever those are (and no, there's
> no schedule).
>
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.
It would break timezone reporting for historical Moscow timestamps, ie
> they'd be printed as GMT-3 whether or not that was applicable at the time.
> Don't know whether you care about that.
The column storing datetime is of type "timestamp" and timezone is not
being stored. So should not be an issue for this particular use-case. For
"timestamp with time zone" that was definitely an issue.
By the way won't that be issue anyways once the Moscow timezone is
corrected in upgraded postgres version?
Regards...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-09-17 19:52:23 | Re: Regarding timezone |
| Previous Message | Tom Lane | 2014-09-17 18:31:17 | Re: Regarding timezone |