Re: Refactoring: Use soft error reporting for *_opt_error functions - Mailing list pgsql-hackers

From Amul Sul
Subject Re: Refactoring: Use soft error reporting for *_opt_error functions
Date
Msg-id CAAJ_b96y6Fh2N11UmRM7rpg2Fb1+nuRfKzc1nZT8d9Ef7P-qkQ@mail.gmail.com
Whole thread Raw
In response to Re: Refactoring: Use soft error reporting for *_opt_error functions  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Fri, Sep 5, 2025 at 10:28 AM Michael Paquier <michael@paquier.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



pgsql-hackers by date:

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