Re: Refactoring: Use soft error reporting for *_opt_error functions

jian he <jian.universality@gmail.com>

From: jian he <jian.universality@gmail.com>

To: Amul Sul <sulamul@gmail.com>

Cc: Dean Rasheed <dean.a.rasheed@gmail.com>, Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-09-03T14:41:14Z

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 →

Fix two comments in numeric.c
- 0c7f10302820 19 (unreleased) landed
Switch some numeric-related functions to use soft error reporting
- 4246a977bad6 19 (unreleased) landed
Change pg_lsn_in_internal() to use soft error reporting
- ae453120085f 19 (unreleased) landed

On Wed, Sep 3, 2025 at 7:52 PM Amul Sul <sulamul@gmail.com> wrote:
>

--- a/src/include/utils/numeric.h
+++ b/src/include/utils/numeric.h
-extern int32 numeric_int4_opt_error(Numeric num, bool *have_error);
.....
+extern int32 numeric_int4_safe(Numeric num, Node *escontext);

would any extensions using these functions (such as
numeric_int4_opt_error) may encounter upgrade compatibility issues in
the future?