Re: Updating our timezone code in the back branches

From: Greg Stark <stark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Updating our timezone code in the back branches
Date: 2016-07-19 16:13:02
Message-ID: CAM-w4HNT1=BAo+=Hfy7bWLv_b8XVcByfkhF8_UUoUDFTOR-gSA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 18, 2016 at 8:09 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> There are also several bug fixes that affect interpretation of dates after
> 2037, a year that's getting closer all the time.

Does this represent a data incompatibility for databases that could
contain such dates already? That is, would this be changing the dates
their database contains?

We don't really have a solution for that kind of change but we should
highlight it fairly prominently and it would be nice if we gave people
a query that would search for any affected dates in a column.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-07-19 16:41:30 Re: Updating our timezone code in the back branches
Previous Message Magnus Hagander 2016-07-19 16:00:32 Re: Updating our timezone code in the back branches