Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp - Mailing list pgsql-hackers

From Amul Sul
Subject Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp
Date
Msg-id CAAJ_b9557PL0zUk3H4hr83Mq8SY8_ypWDf2BzMOtuh7xH8N3Ng@mail.gmail.com
Whole thread Raw
In response to Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp
List pgsql-hackers
On Mon, Dec 1, 2025 at 12:32 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Fri, Nov 28, 2025 at 09:46:43AM +0530, Amul Sul wrote:
> > I have attached patch 0002 that renames it. I also updated patch 0001
> > to accommodate Amit's comment suggestions.
>
> Thanks, applied this one after more tweaks.  Regarding 0002, just
> doing a renaming makes me a bit uncomfortable after a second look.
> Another way to look at the problem while being consistent would be to
> convert date2timestamp_no_overflow() to use soft error reports,
> requiring its caller in selfuncs.c to use an error context node.  I
> cannot get really excited at the end just for the sake of the planner
> stats.
>

Understood. Thanks for committing the patch.

> 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.

Regards,
Amul



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: Migrate to autoconf 2.72?
Next
From: Amul Sul
Date:
Subject: Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions