Re: Warning-suppression fixes we ought to back-patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Warning-suppression fixes we ought to back-patch
Date: 2026-02-25 15:57:38
Message-ID: 185183.1772035058@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> On 24.02.26 17:24, Tom Lane wrote:
>> While we've done a lot of const-cleanliness work recently, this patch
>> should be enough to silence most of the cast-away-const warnings I'm
>> seeing in the BF back branches. Only "midge" is showing them at the
>> moment, but more people will be seeing them as gcc 16 gets more
>> widespread.

> These warnings came in from the new glibc version 2.43, not from the
> compiler.

Ah. Although I suppose you also need a sufficiently late-model
compiler, to understand the annotations on strchr() and friends.
Anyway, thanks for the correction.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2026-02-25 16:03:19 Re: Adding REPACK [concurrently]
Previous Message Maxim Orlov 2026-02-25 15:56:08 Re: POC: make mxidoff 64 bits