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

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Amul Sul <sulamul(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp
Date: 2025-12-02 08:21:34
Message-ID: CA+HiwqE0m5xf9axiLLq8FJHdb8kQa-bMyYKgNeJro3JgPvJm0A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 1, 2025 at 9:02 PM Amul Sul <sulamul(at)gmail(dot)com> wrote:
> On Mon, Dec 1, 2025 at 12:32 PM Michael Paquier <michael(at)paquier(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ajin Cherian 2025-12-02 08:27:57 Re: Improve pg_sync_replication_slots() to wait for primary to advance
Previous Message Michael Paquier 2025-12-02 08:11:54 Re: Remove useless pointer advance in StatsShmemInit()