Re: IANA timezone abbreviations versus timezone_abbreviations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "Andreas Karlsson" <andreas(at)proxel(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: IANA timezone abbreviations versus timezone_abbreviations
Date: 2024-12-29 22:56:38
Message-ID: 3722717.1735512998@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl> writes:
> I think it would be good to add some additional clarify here. It was
> fairly confusing to me. Especially the last sentence, due to the use of
> "active zone", even though it's really talking about the currently
> active abbreviations list. Probably my confusion mostly came from the
> fact that I wasn't aware that timezone abbreviations were localized, but
> I doubt I'm alone in not knowing this. Maybe something like this (feel
> free to improve further):

Hmm, I don't like your phrasing using "IANA time zone database",
because that makes it sound like we'll take any abbreviation that's
found anywhere in that whole data set. What the proposal actually
does is to recognize any abbreviation that is used, or has been
used in the past, in the IANA time zone selected by our current
timezone setting. (And, perhaps more to the point, to give it the
meaning it has or had in that zone.) Not sure about concise wording
for that.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-12-30 01:08:31 Re: An improvement of ProcessTwoPhaseBuffer logic
Previous Message Jelte Fennema-Nio 2024-12-29 22:49:55 Re: IANA timezone abbreviations versus timezone_abbreviations