Re: Updating our timezone code in the back branches - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Updating our timezone code in the back branches
Date
Msg-id CAM-w4HNT1=BAo+=Hfy7bWLv_b8XVcByfkhF8_UUoUDFTOR-gSA@mail.gmail.com
Whole thread Raw
In response to Updating our timezone code in the back branches  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Updating our timezone code in the back branches  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Jul 18, 2016 at 8:09 PM, Tom Lane <tgl@sss.pgh.pa.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



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Updating our timezone code in the back branches
Next
From: Tom Lane
Date:
Subject: Re: Updating our timezone code in the back branches