On 09/17/2014 12:26 PM, Dev Kumkar wrote:
> On Thu, Sep 18, 2014 at 12:01 AM, Tom Lane <tgl@sss.pgh.pa.us
> <mailto:tgl@sss.pgh.pa.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.
They will.
>
> 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?
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
>
> Regards...
--
Adrian Klaver
adrian.klaver@aklaver.com
