| From: | Nacho Caballero <nachocab(at)gmail(dot)com> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Subject: | Bug in tzdata 2022g |
| Date: | 2023-05-06 08:35:30 |
| Message-ID: | CAF1W7uz4HcZkuo-c03F0siFQv951rosV79ahi5K4QPmc7f4KJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-05-06 14:50:25 | Re: Bug in tzdata 2022g |
| Previous Message | Tony Shelver | 2023-05-06 05:08:21 | Re: Unable to install Application Stack Builder |