Re: [PATCH] Add error_on_null() to produce an error if the input is null

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Vik Fearing <vik@postgresfriends.org>

Cc: Joel Jacobson <joel@compiler.org>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-10-21T08:16:32Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Bump catalog version for new function error_on_null()
- 2519fa836235 19 (unreleased) landed
Add error_on_null(), checking if the input is the null value
- 2b75c38b707a 19 (unreleased) landed

On Sun, Aug 31, 2025 at 04:16:42PM +0200, Vik Fearing wrote:
> Thank you.  Updated.

This one was marked as committer, so I am looking at it.

The original proposal can also be tracked in this message, where you
want to have a trick for SQL bodies to be able to detect if exactly
one row is returned:
https://www.postgresql.org/message-id/de94808d-ed58-4536-9e28-e79b09a534c7@app.fastmail.com

Why not if this simple solution works for you, using error_on_null()
as the function name.  I'll double-check the whole, probably tomorrow.
--
Michael