Re: jsonapi: scary new warnings with LTO enabled - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: jsonapi: scary new warnings with LTO enabled
Date
Msg-id CAOYmi+kKB7CLsJEauEH8afsZLx2f2RdLtDPLAW2kHztPcR7oHA@mail.gmail.com
Whole thread Raw
In response to Re: jsonapi: scary new warnings with LTO enabled  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: jsonapi: scary new warnings with LTO enabled
List pgsql-hackers
On Tue, Apr 22, 2025 at 3:10 AM Daniel Gustafsson <daniel@yesql.se> wrote:
> My preference is that no operation can silently work on a failed object, but
> it's not a hill (even more so given where we are in the cycle).

Hm, okay. Something to talk about with Andrew and Peter, maybe.

> 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,
--Jacob



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: Row pattern recognition
Next
From: Steve Chavez
Date:
Subject: Re: Allow database owners to CREATE EVENT TRIGGER