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

Поиск
Список
Период
Сортировка
От Dean Rasheed
Тема Re: Refactoring: Use soft error reporting for *_opt_error functions
Дата
Msg-id CAEZATCVeHvmd-bWZmrhPUUDXbmwrNP3FB=fXwtDkXQjQthvxew@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Refactoring: Use soft error reporting for *_opt_error functions  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Refactoring: Use soft error reporting for *_opt_error functions
Список pgsql-hackers
On Thu, 4 Sept 2025 at 01:18, Michael Paquier <michael@paquier.xyz> wrote:
>
> I'd be pretty much OK with this version of the patch, plus a few
> tweaks.

Agreed.

In numeric_div_safe():

+div_error:
+    ereturn(escontext, NULL,
+            errcode(ERRCODE_DIVISION_BY_ZERO),
+            errmsg("division by zero"));

I would make that label something more specific like "division_by_zero".

> Dean, you have commented on this patch before me and the numeric code
> is something you have touched more than me lately (the LSN part is
> tainted with my fingerprints, but it's minimal here).  Would you
> prefer handle this patch yourself?  I'm OK to perform a final lookup
> of it for commit, just won't get in your way if you have been looking
> at it seriously.

I don't mind. I haven't looked at it too closely, but I'm broadly
happy with it. I think any issues are probably now minor cosmetic
things, so if you've been looking in more detail and are happy to
commit it, then go ahead. Otherwise, I can take it if you prefer.

Regards,
Dean



В списке pgsql-hackers по дате отправления: