Re: IANA timezone abbreviations versus timezone_abbreviations

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

On Mon Dec 16, 2024 at 8:57 PM CET, Tom Lane wrote:
> Andreas Karlsson <andreas(at)proxel(dot)se> writes:
>> On 12/13/24 12:33 AM, Tom Lane wrote:
>> I am not convinced this is an improvement. While this patch removes the
>> round-trip hazard it also makes it confusing to use the
>> timezone_abbreviations GUC since it can be overridden by IANA data based
>> on your current timezone. So you need to know all the, sometimes weird,
>> names for your current timezone. Seems unnecessarily hard to reason
>> about and wouldn't most people who use timezone_abbreviations rely on
>> the current behavior?
>
> Presumably they're not that weird to the locals?
>
> I am not sure what you mean by "people who use
> timezone_abbreviations". I think that's about everyone --- it's
> not like the default setting doesn't contain any abbreviations.
> (If it didn't then we'd not have such a problem...)

Maybe changing the default value of timezone_abbreviations is a better
solution to the problem, or in addition to the proposed patch.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-12-29 22:56:38 Re: IANA timezone abbreviations versus timezone_abbreviations
Previous Message Jelte Fennema-Nio 2024-12-29 22:37:39 Re: IANA timezone abbreviations versus timezone_abbreviations