| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Andrew McNamara <andrewm(at)object-craft(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Aussie timezone database changes incoming |
| Date: | 2014-10-04 20:25:15 |
| Message-ID: | 20141004202515.GS14522@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Oct 4, 2014 at 03:01:45PM -0500, Jim Nasby wrote:
> On 10/4/14, 2:58 PM, Bruce Momjian wrote:
> >>I've committed changes for this in advance of the upcoming 9.4beta3
> >>>release. Hopefully, if this is seriously bad for anyone, we'll hear
> >>>about it from beta testers before it gets into any official back-branch
> >>>releases.
> >The changes for the Russian Federation timezones taking effect October
> >26 reinforces our need to get a new set of minor releases out soon. In
> >fact, those storing future dates might already need those updates.
> This is why I wish we had a data type that stored the timezone that was originally in effect. :/
Uh, if we stored the _offset_ that was in effect at the time of storage,
it would actually be _worse_ because the new timezone database would not
adjust existing stored values. If we stored the name of the time zone,
I am not sure how that would help us here.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-10-04 21:03:24 | Re: Aussie timezone database changes incoming |
| Previous Message | Jim Nasby | 2014-10-04 20:13:30 | Re: Replication identifiers, take 3 |