From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ted Yu <yuzhihong@gmail.com>
cc: Andrew Dunstan <andrew@dunslane.net>, Amul Sul <sulamul@gmail.com>,
        Andres Freund <andres@anarazel.de>,
        Alexander Korotkov <aekorotkov@gmail.com>,
        Robert Haas <robertmhaas@gmail.com>,
        "David G. Johnston" <david.g.johnston@gmail.com>,
        Corey Huinker <corey.huinker@gmail.com>,
        Alvaro Herrera <alvherre@alvh.no-ip.org>,
        Joe Conway <mail@joeconway.com>,
        Nikita Glukhov <n.gluhov@postgrespro.ru>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Error-safe user functions
In-reply-to: 
 <CALte62yRJwVzp5CxRRsumXV-0Y1JBHZguRGFMQt2fgwH0nUusw@mail.gmail.com>
References: <4009543.1670422833@sss.pgh.pa.us>
 <20221208215836.3naznqmal2m32hzc@awork3.anarazel.de>
 <512551.1670540229@sss.pgh.pa.us>
 <20221209023351.l362yejerfoq3lfp@awork3.anarazel.de>
 <633426.1670554790@sss.pgh.pa.us>
 <01ff2051-806d-af2f-4f9e-793f7ba9a3f8@dunslane.net>
 <778369.1670598993@sss.pgh.pa.us>
 <5aaf7c66-9df9-21a9-1ff4-02c7848def52@dunslane.net>
 <3bac9841-fe07-713d-fa42-606c225567d6@dunslane.net>
 <1436686.1670701118@sss.pgh.pa.us>
 <2b1e7d56-6f37-bad9-9702-053ab55ecf60@dunslane.net>
 <1805344.1670779451@sss.pgh.pa.us>
 <b54e97be-7316-2cab-6969-bfac6ec88ca6@dunslane.net>
 <1863335.1670783397@sss.pgh.pa.us>
 <CAAJ_b97KeDWUdpTKGOaFYPv0OicjOu6EW+QYWj-Ywrgj_aEy1g@mail.gmail.com>
 <2687377.1671033604@sss.pgh.pa.us> <2966981.1671057469@sss.pgh.pa.us>
 <1964968.1671727440@sss.pgh.pa.us>
 <9c8f22f2-7a37-fc4d-8e9f-3431c0d09c5a@dunslane.net>
 <CALte62wLvzOAigC5bdsxX73WGGi5zX5OiYmjkNYcRFkHo8nMYQ@mail.gmail.com>
 <2791143.1671830567@sss.pgh.pa.us> <CALte62yRJwVzp5CxRRsumXV-0Y1JBHZguRGFM!
 Qt2fgwH0nUusw@mail.gmail.com>
Comments: In-reply-to Ted Yu <yuzhihong@gmail.com>
	message dated "Sat, 24 Dec 2022 01:51:10 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2912238.1671896891.1@sss.pgh.pa.us>
Date: Sat, 24 Dec 2022 10:48:11 -0500
Message-ID: <2912239.1671896891@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2912239.1671896891%40sss.pgh.pa.us>
Precedence: bulk

Ted Yu <yuzhihong@gmail.com> writes:
> On Fri, Dec 23, 2022 at 1:22 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Yes, it is.  We don't want a query-cancel transformed into a soft error.

> The same regex, without user interruption, would exhibit an `invalid
> regular expression` error.

On what grounds do you claim that?  The timing of arrival of the SIGINT
is basically chance --- it might happen while we're inside backend/regex,
or not.  I mean, sure you could claim that a bad regex might run a long
time and thereby be more likely to cause the user to issue a query
cancel, but that's a stretched line of reasoning.

			regards, tom lane