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

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Amul Sul <sulamul(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Refactoring: Use soft error reporting for *_opt_error functions
Date: 2025-10-05 22:19:49
Message-ID: CACJufxFfVt7Jx9_j=juxXyP-6tznN8OcvS9E-QSgp0BrD8KUgA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 5, 2025 at 12:58 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> Applied after a few tweaks, including changes to the comments, the
> suggestion of "division_by_zero" for the goto labels, and splitting
> the patch into two parts for pg_lsn and numeric.

/*
* Internal version of int8_numeric() with support for soft error reporting.
*/
int64
numeric_int8_safe(Numeric num, Node *escontext)

the above comment "int8_numeric" should be "numeric_int8"?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ilyasov Ian 2025-10-05 22:30:53 RE: Resetting recovery target parameters in pg_createsubscriber
Previous Message Tom Lane 2025-10-05 19:14:44 Re: psql client does not handle WSAEWOULDBLOCK on Windows