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

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Amul Sul <sulamul(at)gmail(dot)com>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Refactoring: Use soft error reporting for *_opt_error functions
Date: 2025-09-03 14:41:14
Message-ID: CACJufxFQFdEYfi9edi_dm7A_JJX4rH5_Pn=Kk2NJM_h5M6p-Uw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 3, 2025 at 7:52 PM Amul Sul <sulamul(at)gmail(dot)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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-09-03 14:42:33 Re: Solaris compiler status
Previous Message Peter Eisentraut 2025-09-03 14:05:09 expand virtual generated columns in get_relation_constraints()