Re: Add returns_nonnull to infallible allocators - Mailing list pgsql-hackers

From Tristan Partin
Subject Re: Add returns_nonnull to infallible allocators
Date
Msg-id DJROVLR64UE7.2644YDIMK75FA@partin.io
Whole thread
In response to Add returns_nonnull to infallible allocators  ("Tristan Partin" <tristan@partin.io>)
List pgsql-hackers
On Mon Jul 6, 2026 at 6:10 PM UTC, Tristan Partin wrote:
> Postgres memory allocators, by default, ERROR out on memory allocation
> failures. An ERROR leads to a longjmp, which means that the caller of
> the allocator will never see a NULL return value. We can explicitly let
> the compiler know about this behavior by adding the returns_nonnull
> attribute to the allocators that follow this behavior. Postgres does
> support _extended versions of some of the allocators that take a flaks
> argument. The caller can provide the MCXT_ALLOC_NO_OOM flag to these
> allocators to request that they return NULL on allocation failure
> instead of ERROR-ing out. The _extended allocators cannot be marked as
> returns_nonnull because of that.
>
> By using returns_nonnull, we can help the compiler to optimize call
> sites.

...

--
Tristan Partin
PostgreSQL Contributors Team
AWS (https://aws.amazon.com)

Attachment

pgsql-hackers by date:

Previous
From: "Tristan Partin"
Date:
Subject: Add returns_nonnull to infallible allocators
Next
From: Robert Haas
Date:
Subject: Re: implement CAST(expr AS type FORMAT 'template')