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

From: Amul Sul <sulamul(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, jian he <jian(dot)universality(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-09-05 05:12:26
Message-ID: CAAJ_b96y6Fh2N11UmRM7rpg2Fb1+nuRfKzc1nZT8d9Ef7P-qkQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 5, 2025 at 10:28 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Fri, Sep 05, 2025 at 08:10:00AM +0900, Michael Paquier wrote:
> > Sure. I'll handle it. Thanks.
>
> Applied after a few tweaks, including changes to the comments, the
> suggestion of "division_by_zero" for the goto labels, and splitting
> the patch into two parts for pg_lsn and numeric.

Thanks for improving and committing the patch. I see now that two
separate commits were definitely needed, and I should have submitted
them that way. Thank you again for splitting it into two parts.

Regards,
Amul

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2025-09-05 05:13:04 pg_dump, pg_dumpall, pg_restore HELP progname descrption of "--no-table-access-method" is wrong?
Previous Message Michael Paquier 2025-09-05 05:11:18 Re: Update outdated references to SLRU ControlLock