Re: IANA timezone abbreviations versus timezone_abbreviations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, "Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Andreas Karlsson" <andreas(at)proxel(dot)se>
Subject: Re: IANA timezone abbreviations versus timezone_abbreviations
Date: 2025-01-10 01:21:04
Message-ID: 2321184.1736472064@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> 0003 is new work that fixes the pg_timezone_abbrevs view so
> that its output matches the new behavior.

Hmph ... the cfbot doesn't like that one bit. It appears that the
"LMT" abbrev is known in my machine's system-provided tzdata tree,
but not when building our own timezone files. I wonder if this is
exposing an existing bug (perhaps our copy of zic is too far out of
date?). Will look into it tomorrow.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-01-10 01:26:04 Re: Log a warning in pg_createsubscriber for max_slot_wal_keep_size
Previous Message Michail Nikolaev 2025-01-10 01:09:42 Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?