Re: Update our timezone code to IANA tzcode2026b

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Update our timezone code to IANA tzcode2026b
Date: 2026-08-03 10:06:52
Message-ID: 46830a2d-0526-4945-a4e2-e649de6e815a@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11.07.26 17:18, Tom Lane wrote:
> Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
>> I know you have already reported this upstream, but here are some
>> patches to silence the resulting warnings on MSVC.
>
> Since Eggert doesn't seem to want to do anything about these,
> I was planning on just ignoring them (and have already adjusted
> my warning-scraping script to do so). I don't think inserting
> diffs from tzdb upstream is a good tradeoff, so I definitely
> don't like your 0001. I'd be okay with 0002's solution (suppress
> the unary-minus complaint globally). I might hold my nose for
> 0003, but you say it doesn't seem to work, so ...

How about we just disable these warnings for this file, as in the
attached patch.

Attachment Content-Type Size
v2-0001-Fix-MSVC-warnings-from-new-timezone-code.patch text/plain 1.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yilin Zhang 2026-08-03 10:13:24 Re: [PATCH] Add NESTED_STATEMENTS option to EXPLAIN
Previous Message Reshmithaa 2026-08-03 10:00:05 Catcache rehash hits MaxAllocSize (1GB) and errors with "invalid memory alloc request size" on very large numbers of relations