Re: Ignoring symlinks when recovering time zone identifiers in initdb

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Florian Weimer <fw(at)deneb(dot)enyo(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Andrew Gierth <rhodiumtoad(at)postgresql(dot)org>
Subject: Re: Ignoring symlinks when recovering time zone identifiers in initdb
Date: 2025-09-14 16:21:10
Message-ID: 420337.1757866870@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Florian Weimer <fw(at)deneb(dot)enyo(dot)de> writes:
>> There's a story making the rounds that the removal of the
>> /usr/share/zoneinfo/US/Pacific etc. in Debian broke installations.
>> These identifiers should not be used, but they may get picked by
>> initdb if they are shorter than the alternatives.

> Ugh. (Fortunately, I don't think fixing this is any harder than
> editing the timezone entries in postgresql.conf.)

BTW, I wonder why 23bd3cec6 ("Attempt to identify system timezone by
reading /etc/localtime symlink") didn't help here. It looks to me
like Debian follows the convention of /etc/localtime being a symlink,
so we should have chosen whichever zone is the system's setting
and never fallen back to our zone-name heuristics at all.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2025-09-14 17:08:49 Re: PostgreSQL 18 GA press release draft
Previous Message Tom Lane 2025-09-14 15:55:42 Re: Ignoring symlinks when recovering time zone identifiers in initdb