Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Amul Sul <sulamul@gmail.com>

Cc: Amit Langote <amitlangote09@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-12-02T00:32:15Z

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 →

Update some timestamp[tz] functions to use soft-error reporting
- 713d9a847e64 19 (unreleased) landed
Switch some date/timestamp functions to use the soft error reporting
- d03668ea0566 19 (unreleased) landed
Switch some numeric-related functions to use soft error reporting
- 4246a977bad6 19 (unreleased) cited

On Mon, Dec 01, 2025 at 05:31:43PM +0530, Amul Sul wrote:
> On Mon, Dec 1, 2025 at 12:32 PM Michael Paquier <michael@paquier.xyz> wrote:
>> There were two more functions that btree_gin.c is pointing at that
>> could to the switch: timestamp->timestamptz and its opposite.  This
>> also shaves some code, which is nice.  Please see the attached.
> 
> Yes, the patch looks good to me.

Thanks for double-checking.  Applied this one as well.
--
Michael