Re: Add compiler option -fstrict-flex-arrays=1

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Tristan Partin <tristan(at)partin(dot)io>
Cc: Greg Burd <greg(at)burd(dot)me>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, David Geier <geidav(dot)pg(at)gmail(dot)com>
Subject: Re: Add compiler option -fstrict-flex-arrays=1
Date: 2026-11-04 09:08:29
Message-ID: fb11f9be-cf58-4a0f-bb87-0dad65797ac2@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03.11.26 06:28, Tristan Partin wrote:
> On Wed Oct 28, 2026 at 8:04 AM UTC, Peter Eisentraut wrote:
>> On 27.10.26 16:51, Tristan Partin wrote:
>>> We could define a pg_attribute_strict_flex_array() macro and add it to
>>> the entry in WordEntryPosVector1. We can add a comment to the macro
>>> indicating how and why it should be used since it'll likely be a little
>>> non-obvious, but we could continue to keep bounds checking on
>>> WordEntryPosVector1.
>>
>> Something like in the attached patch 0002?
>>
>> (Patch 0001 is unchanged.)
>
> Yep, that is exactly what I had in mind.

Committed, thanks.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-11-04 09:09:19 Re: Emptying oauth_validator_libraries doesn't stop OAuth logins
Previous Message Ayoub Kazar 2026-11-04 08:57:56 Re: Fix DEFAULT marker handling in COPY FROM ... HEADER MATCH