From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: More tzdb fun: POSIXRULES is being deprecated upstream |
Date: | 2020-06-19 20:02:03 |
Message-ID: | CA+TgmoZcu2Z1uDm5OKW=P9pc=oQ7534GhuiM1_EbmRq54sQJ8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 19, 2020 at 3:55 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The code delta is small enough that I don't foresee any real maintenance
> problem if we let the back branches differ from HEAD/v13 on this point.
> What I'm concerned about is that people depending on the existing
> behavior are likely to wake up one fine morning and discover that it's
> broken after a routine tzdata update. I think that it'd be a better
> user experience for them to see a release-note entry in a PG update
> release explaining that this will break and here's what to do to fix it.
I was assuming that if you did an update of the tzdata, you'd notice
if posixrules had been nuked. I guess that wouldn't help people who
are using the system tzdata, though. It might be nice to know what
Debian, RHEL, etc. plan to do about this, but I'm not sure how
practical it is to find out.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-06-19 20:22:04 | Re: More tzdb fun: POSIXRULES is being deprecated upstream |
Previous Message | Robert Haas | 2020-06-19 20:00:07 | Re: Parallel Seq Scan vs kernel read ahead |