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 1p2yiu-0007Aj-9v for pgsql-hackers@arkaria.postgresql.org; Wed, 07 Dec 2022 18:00:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p2yit-0003ni-8E for pgsql-hackers@arkaria.postgresql.org; Wed, 07 Dec 2022 18:00:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p2yis-0003lo-VH for pgsql-hackers@lists.postgresql.org; Wed, 07 Dec 2022 18:00:46 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p2yio-00048B-T5 for pgsql-hackers@lists.postgresql.org; Wed, 07 Dec 2022 18:00:45 +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 2B7I0c6s4043605; Wed, 7 Dec 2022 13:00:38 -0500 From: Tom Lane cc: Andres Freund , Corey Huinker , Andrew Dunstan , Alvaro Herrera , Joe Conway , Robert Haas , Nikita Glukhov , PostgreSQL Hackers Subject: Re: Error-safe user functions In-reply-to: <4042204.1670435489@sss.pgh.pa.us> References: <85e40849-4458-bbb9-62ee-d9e7faf0c7dc@dunslane.net> <3323802.1670263204@sss.pgh.pa.us> <3496391.1670276406@sss.pgh.pa.us> <20221205234734.sab3fuxy6q2sokjd@alap3.anarazel.de> <3518534.1670285891@sss.pgh.pa.us> <20221206005607.lxcrazckoalptwds@alap3.anarazel.de> <3523582.1670288815@sss.pgh.pa.us> <40ff1ed1-4245-e343-bffa-c7755b031492@dunslane.net> <3889877.1670358069@sss.pgh.pa.us> <20221207173427.7jmjd3fsfuydh6th@awork3.anarazel.de> <4042204.1670435489@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Wed, 07 Dec 2022 12:51:29 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4043603.1670436038.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 07 Dec 2022 13:00:38 -0500 Message-ID: <4043604.1670436038@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I wrote: > Andres Freund writes: >> Is there a guarantee that input functions are stable or immutable? > There's a project policy that that should be true. That justifies > marking things like record_in as stable --- if the per-column input > functions could be volatile, record_in would need to be as well. > There are other dependencies on it; see e.g. aab353a60, 3db6524fe. I dug in the archives and found the thread leading up to aab353a60: https://www.postgresql.org/message-id/flat/AANLkTik8v7O9QR9jjHNVh62h-COC1B= 0FDUNmEYMdtKjR%40mail.gmail.com regards, tom lane