From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: Andrew Dunstan <andrew@dunslane.net>, Amul Sul <sulamul@gmail.com>,
        Andres Freund <andres@anarazel.de>,
        Alexander Korotkov <aekorotkov@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: 
 <CA+TgmoYAfYDL-=FcgzMhWWqUxtsnbu3ShrGMaG+ah4Kfn_fkzw@mail.gmail.com>
References: <4009543.1670422833@sss.pgh.pa.us>
 <6acddf68-7cb7-e9e7-a5a7-0abc87b3c55b@dunslane.net>
 <CAKFQuwYdQqQru9tpMpY4JpCEJ8OeN8kwmBG6DY2QyzE+5znA6Q@mail.gmail.com>
 <4111458.1670444176@sss.pgh.pa.us> <3211.1670452341@sss.pgh.pa.us>
 <20221207233518.sudtaxn6omtvpzvr@awork3.anarazel.de>
 <186288.1670517119@sss.pgh.pa.us>
 <CA+TgmoZOhQ8FfWH9_r58tLtb=AwBn=7ugO2PHh6moR8jhYviUA@mail.gmail.com>
 <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> <2687377.1671033604@sss.p!
 gh.pa.us> <3038346.1671060258@sss.pgh.pa.us>
 <CA+TgmobdvGSCNWvD2OYAajjUaS+vYKXYCsSSdk=vrUJaZ2TbOg@mail.gmail.com>
 <3564577.1671142683@sss.pgh.pa.us> <3819056.1671215496@sss.pgh.pa.us>
 <CA+TgmoYAfYDL-=FcgzMhWWqUxtsnbu3ShrGMaG+ah4Kfn_fkzw@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Mon, 19 Dec 2022 11:34:39 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <936417.1671468277.1@sss.pgh.pa.us>
Date: Mon, 19 Dec 2022 11:44:37 -0500
Message-ID: <936418.1671468277@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/936418.1671468277%40sss.pgh.pa.us>
Precedence: bulk

Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Dec 16, 2022 at 1:31 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> The reg* functions probably need a unified plan as to how far
>> down we want to push non-error behavior.  The rest of these
>> I think just require turning the crank along the same lines
>> as in functions already dealt with.

> I would be in favor of an aggressive approach.

I agree that anything based on implementation concerns is going
to look pretty unprincipled to end users.  However ...

> It also doesn't seem too bad from an implementation point of view to
> try to cover all the caes.

... I guess you didn't read my remarks upthread about regtypein.
I do not want to try to make gram.y+scan.l non-error-throwing.

			regards, tom lane