Re: jsonapi: scary new warnings with LTO enabled

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: jsonapi: scary new warnings with LTO enabled
Date: 2025-04-23 09:35:15
Message-ID: 30D7779C-8EE0-48BC-B27C-E7389880F713@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 23 Apr 2025, at 02:01, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> On Tue, Apr 22, 2025 at 3:10 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:

>> The attached
>> v3 allocates via the JSON api, no specific error handling should be required as
>> it's already handled today.
>
> pgindent shows one whitespace change on my machine (comment
> indentation), but other than that, LGTM! Fuzzers are happy too.

Thanks for confirming, I've pushed this now.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2025-04-23 09:39:32 extension_control_path and "directory"
Previous Message Frédéric Yhuel 2025-04-23 09:27:05 Re: [BUG] temporary file usage report with extended protocol and unnamed portals