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

From Daniel Gustafsson
Subject Re: jsonapi: scary new warnings with LTO enabled
Date
Msg-id 0C92C876-09A3-483C-82C5-E26F0C1B34B5@yesql.se
Whole thread Raw
In response to Re: jsonapi: scary new warnings with LTO enabled  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: jsonapi: scary new warnings with LTO enabled
List pgsql-hackers
> On 21 Apr 2025, at 20:58, Jacob Champion <jacob.champion@enterprisedb.com> wrote:

> Personally, I'm fine with can't-fail APIs, as long as they're
> documented as such. (I think the deferred error API was probably
> chosen so that src/common JSON clients could be written without a lot
> of pain?)

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).  The attached
v3 allocates via the JSON api, no specific error handling should be required as
it's already handled today.

--
Daniel Gustafsson


Attachment

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER
Next
From: Frédéric Yhuel
Date:
Subject: Re: [BUG] temporary file usage report with extended protocol and unnamed portals