| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Subject: | Re: Converting contrib SQL functions to new style |
| Date: | 2021-04-14 17:19:55 |
| Message-ID: | CA+TgmoYQB1qxb=v9xVi09-f_HRDDqwUwfcuNpsZ2SF-ePpWJcw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 14, 2021 at 10:49 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The situation of interest is where you are trying to install an extension
> into a schema that also contains malicious objects. We've managed to make
> most of the commands you might use in an extension script secure against
> that situation, and Noah wants to hold SQL-function creation to that same
> standard.
Oh, I was forgetting that the creation schema has to be first in your
search path. :-(
Does the idea of allowing the creation schema to be set separately
have any legs? Because it seems like that would help here.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-04-14 17:27:22 | Re: Possible typo/unclear comment in joinpath.c |
| Previous Message | Mark Dilger | 2021-04-14 17:18:30 | Re: Converting contrib SQL functions to new style |