Re: Update timezone to C99

2025-11-19 Thread Tom Lane
Peter Eisentraut writes: > On 14.11.25 22:11, Tom Lane wrote: >> "leapyear" is bool, and I believe these casts-to-int were put in to >> suppress compiler bleats about up-casting that to int. This probably >> dates from when we equated bool to char, and maybe it's moot now, >> but I'm not sure. >

Re: Update timezone to C99

2025-11-19 Thread Peter Eisentraut
On 14.11.25 22:11, Tom Lane wrote: Peter Eisentraut writes: On 12.11.25 19:02, Tom Lane wrote: Hm, I've had "re-sync TZ code with upstream" on my TODO list for several years now. I believe there's been quite a bit of churn upstream since tzcode2020d, some of it oriented towards this same issu

Re: Update timezone to C99

2025-11-14 Thread Tom Lane
Peter Eisentraut writes: > On 12.11.25 19:02, Tom Lane wrote: >> Hm, I've had "re-sync TZ code with upstream" on my TODO list for >> several years now. I believe there's been quite a bit of churn >> upstream since tzcode2020d, some of it oriented towards this same >> issue of code modernization.

Re: Update timezone to C99

2025-11-14 Thread Peter Eisentraut
On 12.11.25 19:02, Tom Lane wrote: Peter Eisentraut writes: To fix that, I re-downloaded the upstream code (same version as before), applied the fixes described in src/timezone/README, except those related to the integer types, and then put back the PostgreSQL-specific code and massaged things

Re: Update timezone to C99

2025-11-12 Thread Tom Lane
Peter Eisentraut writes: > To fix that, I re-downloaded the upstream code (same version as before), > applied the fixes described in src/timezone/README, except those related > to the integer types, and then put back the PostgreSQL-specific code and > massaged things to remove irrelevant differ