| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ted Yu <yuzhihong(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Amul Sul <sulamul(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Joe Conway <mail(at)joeconway(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Error-safe user functions |
| Date: | 2022-12-23 21:22:47 |
| Message-ID: | 2791143.1671830567@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ted Yu <yuzhihong(at)gmail(dot)com> writes:
> In makeItemLikeRegex :
> + /* See regexp.c for explanation */
> + CHECK_FOR_INTERRUPTS();
> + pg_regerror(re_result, &re_tmp, errMsg,
> sizeof(errMsg));
> + ereturn(escontext, false,
> Since an error is returned, I wonder if the `CHECK_FOR_INTERRUPTS` call is
> still necessary.
Yes, it is. We don't want a query-cancel transformed into a soft error.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ted Yu | 2022-12-23 21:25:42 | Re: Error-safe user functions |
| Previous Message | Ted Yu | 2022-12-23 21:19:07 | Re: Error-safe user functions |