From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>
cc: Christoph Berg <myon@debian.org>,
        PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: UCT (Re: pgsql: Update time zone data files to tzdata release
 2019a.)
In-reply-to: <87blzdacpp.fsf@news-spur.riddles.org.uk>
References: <E1hK8qL-0005yH-VX@gemulon.postgresql.org>
 <20190604085735.GD24018@msg.df7cb.de>
 <87blzdacpp.fsf@news-spur.riddles.org.uk>
Comments: In-reply-to Andrew Gierth <andrew@tao11.riddles.org.uk>
	message dated "Tue, 04 Jun 2019 11:20:14 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <65810.1559662244.1@sss.pgh.pa.us>
Date: Tue, 04 Jun 2019 11:30:44 -0400
Message-ID: <65811.1559662244@sss.pgh.pa.us>
Precedence: bulk

Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
> I believe I pointed out a long, long time ago that this tie-breaking
> strategy was insane, and that the rule should be to prefer canonical
> names and use something else only in the case of a strictly better
> match.

This is assuming that the tzdb data has a concept of a canonical name
for a zone, which unfortunately it does not.  UTC, UCT, Etc/UTC,
and about four other strings are equivalent names for the same zone
so far as one can tell from the installed data.

We could imagine layering some additional data on top of tzdb,
but I don't much want to go there from a maintenance standpoint.

			regards, tom lane