Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jmNWc-0004Yq-Lj for pgsql-hackers@arkaria.postgresql.org; Fri, 19 Jun 2020 20:22:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jmNWb-0005nA-84 for pgsql-hackers@arkaria.postgresql.org; Fri, 19 Jun 2020 20:22:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jmNWa-0005n3-PI for pgsql-hackers@lists.postgresql.org; Fri, 19 Jun 2020 20:22:08 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jmNWY-0007DF-LS for pgsql-hackers@lists.postgresql.org; Fri, 19 Jun 2020 20:22:07 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 05JKM43m1755874; Fri, 19 Jun 2020 16:22:04 -0400 From: Tom Lane To: Robert Haas cc: Peter Eisentraut , PostgreSQL Hackers Subject: Re: More tzdb fun: POSIXRULES is being deprecated upstream In-reply-to: References: <1390.1562258309@sss.pgh.pa.us> <1452646.1592417333@sss.pgh.pa.us> <1753692.1592594861@sss.pgh.pa.us> <1754851.1592596507@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Fri, 19 Jun 2020 16:02:03 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1755872.1592598124.1@sss.pgh.pa.us> Date: Fri, 19 Jun 2020 16:22:04 -0400 Message-ID: <1755873.1592598124@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Robert Haas writes: > On Fri, Jun 19, 2020 at 3:55 PM Tom Lane wrote: >> 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. Yeah, exactly. We can control this easily enough for PG-supplied tzdata trees, but I think a significant majority of actual users are using --with-system-tzdata builds, because we've been telling packagers to do it that way for years. (Nor does changing that advice seem like a smart move.) > 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. There's probably no way to know until it happens :-(. We can hope that they'll be conservative, but it's hard to be sure. It doesn't help that the bigger players rely on glibc: if I understand what Eggert was saying, nuking posixrules would bring tzcode's behavior into closer sync with what glibc does, so they might well feel it's a desirable change. regards, tom lane