From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Converting contrib SQL functions to new style
In-reply-to: <70edea10-6cfe-e83a-5fd5-c290a95abdb7@enterprisedb.com>
References: <3395418.1618352794@sss.pgh.pa.us>
 <70edea10-6cfe-e83a-5fd5-c290a95abdb7@enterprisedb.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@enterprisedb.com>
	message dated "Wed, 01 Sep 2021 09:26:14 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2102170.1630517255.1@sss.pgh.pa.us>
Date: Wed, 01 Sep 2021 13:27:35 -0400
Message-ID: <2102171.1630517255@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2102171.1630517255%40sss.pgh.pa.us>
Precedence: bulk

Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> On 14.04.21 00:26, Tom Lane wrote:
>> Attached are some draft patches to convert almost all of the
>> contrib modules' SQL functions to use SQL-standard function bodies.

> This first patch is still the patch of record in CF 2021-09, but from 
> the subsequent discussion, it seems more work is being contemplated.

Yeah, it looks like we already did the unconditionally-safe part
(i.e. making initdb-created SQL functions use new style, cf 767982e36).

The rest of this is stuck pending investigation of the ideas about
making new-style function creation safer when the creation-time path
isn't secure, so I suppose we should mark it RWF rather than leaving
it in the queue.  Will go do that.

			regards, tom lane