Bug in tzdata 2022g - Mailing list pgsql-bugs

From Nacho Caballero
Subject Bug in tzdata 2022g
Date
Msg-id CAF1W7uz4HcZkuo-c03F0siFQv951rosV79ahi5K4QPmc7f4KJw@mail.gmail.com
Whole thread Raw
Responses Re: Bug in tzdata 2022g  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
There appears to be a bug in the latest postgres release, which uses tzdata 2022g to reflect the recent DST change in Mexico. 

When I convert a UTC timestamp to Mexico City time in 13.10 (Debian 13.10-1.pgdg110+1), I get a one hour difference, which is wrong:

select timezone('America/Mexico_City', '2023-05-06T08:00+00:00'), timezone('America/Bogota', '2023-05-06T08:00+00:00');
      timezone       |      timezone
---------------------+---------------------
 2023-05-06 02:00:00 | 2023-05-06 03:00:00

However, when I run it in PostgreSQL 12.10 (Ubuntu 12.10-1.pgdg20.04+1), I get the right answer (no time difference):

      timezone       |      timezone      
---------------------+---------------------
 2023-05-06 03:00:00 | 2023-05-06 03:00:00

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
Next
From: Tom Lane
Date:
Subject: Re: Bug in tzdata 2022g