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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Vik Fearing <vik(at)postgresfriends(dot)org>
Cc: Joel Jacobson <joel(at)compiler(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Add error_on_null() to produce an error if the input is null
Date: 2025-10-22 01:10:06
Message-ID: aPgu7kwiT4iGo6Ya@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 21, 2025 at 05:16:32PM +0900, Michael Paquier wrote:
> 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.

Applied after a couple of tweaks applied to the code (like added pg_*
to the source function name) and the docs.

And of course I forgot a catversion bump..
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-10-22 02:21:50 Re: Logical Replication of sequences
Previous Message Bryan Green 2025-10-22 01:09:56 Re: [PATCH] Add Windows support for backtrace_functions (MSVC only)