Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p0qVC-0005Tx-EB for pgsql-hackers@arkaria.postgresql.org; Thu, 01 Dec 2022 20:49:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p0qVB-00074o-8W for pgsql-hackers@arkaria.postgresql.org; Thu, 01 Dec 2022 20:49:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p0qVA-00074f-Vj for pgsql-hackers@lists.postgresql.org; Thu, 01 Dec 2022 20:49:48 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p0qV8-0008EB-HU for pgsql-hackers@lists.postgresql.org; Thu, 01 Dec 2022 20:49:48 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 2B1Knghj1703872; Thu, 1 Dec 2022 15:49:42 -0500 From: Tom Lane To: Robert Haas cc: Andrew Dunstan , Corey Huinker , Nikita Glukhov , PostgreSQL Hackers Subject: Re: Error-safe user functions In-reply-to: References: <3bbbb0df-7382-bf87-9737-340ba096e034@postgrespro.ru> <3190059.1665164276@sss.pgh.pa.us> <57b7cc2e-1215-3f43-84e4-6d9f8ad575df@dunslane.net> <3049337.1669008405@sss.pgh.pa.us> <469338a3-da38-160f-23b9-813c261bc1d6@dunslane.net> <1677334.1669918475@sss.pgh.pa.us> <1695760.1669923671@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Thu, 01 Dec 2022 15:12:09 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1703870.1669927782.1@sss.pgh.pa.us> Date: Thu, 01 Dec 2022 15:49:42 -0500 Message-ID: <1703871.1669927782@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > On Thu, Dec 1, 2022 at 2:41 PM Tom Lane wrote: >> I'd be the first to agree that "ereturn" >> doesn't capture that detail very well, but I don't have a better name. >> (And I do like the fact that this name is the same length as "ereport", >> so that we won't end up with lots of reindentation to do.) > I don't think it's sensible to make decisions about important syntax > on the basis of byte-length. Reindenting is a one-time effort; code > clarity will be with us forever. Sure, but without a proposal for a better name, that's irrelevant. regards, tom lane