Request a Demo
Home   >   mailing lists

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

From Amit Langote
Subject Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp
Date
Msg-id CA+HiwqE0m5xf9axiLLq8FJHdb8kQa-bMyYKgNeJro3JgPvJm0A@mail.gmail.com
Whole thread Raw
In response to Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp  (Amul Sul <sulamul@gmail.com>)
List pgsql-hackers
Tree view 
On Mon, Dec 1, 2025 at 9:02 PM Amul Sul <sulamul@gmail.com> wrote:
> 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.

+1, thanks Michael for taking care of this and Amul too.

--
Thanks, Amit Langote

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Remove useless pointer advance in StatsShmemInit()
Next
From: Ajin Cherian
Date:
Subject: Re: Improve pg_sync_replication_slots() to wait for primary to advance