From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
Date: | 2019-07-02 15:47:32 |
Message-ID: | 13181.1562082452@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Long story short, I agree with you that most people probably don't
> care about this very much, but I also agree with Andrew that some of
> the current choices we're making are pretty strange, and I'm not
> convinced as you are that it's impossible to make a principled choice
> between alternatives in all cases. The upstream data appears to
> contain some information about intent; it's not just a jumble of
> exactly-equally-preferred alternatives.
I agree that if there were an easy way to discount the IANA "backward
compatibility" zone names, that'd likely be a reasonable thing to do.
The problem is that those names aren't distinguished from others in
the representation we have available to us (ie, the actual
/usr/share/zoneinfo file tree). I'm dubious that relying on
zone[1970].tab would improve matters substantially; it would fix
some cases, but I don't think it would fix all of them. Resolving
all ambiguous zone-name choices is not the charter of those files.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-07-02 16:32:57 | pgsql: Simplify psql \d's rule for ordering the indexes of a table. |
Previous Message | Peter Geoghegan | 2019-07-02 05:29:50 | pgsql: Remove obsolete nbtree "get root" comment. |
From | Date | Subject | |
---|---|---|---|
Next Message | Alexey Kondratov | 2019-07-02 16:57:21 | Re: Conflict handling for COPY FROM |
Previous Message | Tom Lane | 2019-07-02 15:23:30 | Re: TopoSort() fix |