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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: jian he <jian(dot)universality(at)gmail(dot)com>
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-06 02:18:17
Message-ID: aOMm6Y_H_ZXER9qX@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 06, 2025 at 06:19:49AM +0800, jian he wrote:
> /*
> * 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"?

Yep. The same is true about numeric_int4_safe() where int4_numeric()
is referenced. Will fix, thanks.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Alger 2025-10-06 02:38:21 Re: Improve coments on structures in trigger.c
Previous Message Peter Smith 2025-10-06 02:11:59 Re: [WIP]Vertical Clustered Index (columnar store extension) - take2