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 1lWlt7-0000DD-Am for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Apr 2021 20:13:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lWlt6-000702-4I for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Apr 2021 20:13:24 +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 1lWlt5-0006zu-U0 for pgsql-hackers@lists.postgresql.org; Wed, 14 Apr 2021 20:13:23 +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 1lWlt3-0001ew-G4 for pgsql-hackers@lists.postgresql.org; Wed, 14 Apr 2021 20:13:23 +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 13EKDCdL3583533; Wed, 14 Apr 2021 16:13:12 -0400 From: Tom Lane To: Andrew Dunstan cc: Robert Haas , Noah Misch , PostgreSQL Hackers , Peter Eisentraut Subject: Re: Converting contrib SQL functions to new style In-reply-to: <561ffd5c-3332-abb9-3e60-17b41f025a6b@dunslane.net> References: <3395418.1618352794@sss.pgh.pa.us> <20210414020827.GA1232417@rfd.leadboat.com> <3441172.1618369873@sss.pgh.pa.us> <20210414125811.GB1263822@rfd.leadboat.com> <3489827.1618411777@sss.pgh.pa.us> <3566011.1618422104@sss.pgh.pa.us> <3567049.1618423436@sss.pgh.pa.us> <561ffd5c-3332-abb9-3e60-17b41f025a6b@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Wed, 14 Apr 2021 15:32:28 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3583531.1618431192.1@sss.pgh.pa.us> Date: Wed, 14 Apr 2021 16:13:12 -0400 Message-ID: <3583532.1618431192@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > On 4/14/21 2:03 PM, Tom Lane wrote: >> This may mean that squeezing these contrib changes into v14 is a lost >> cause. We certainly shouldn't try to do what I suggest above for >> v14; but without it, these changes are just moving the security >> issue to a different place rather than eradicating it completely. > Is there anything else we should be doing along the eat your own dogfood > line that don't have these security implications? We can still convert the initdb-created SQL functions to new style, since there's no security threat during initdb. I'll make a patch for that soon. regards, tom lane