| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>, "Kuroda, Hayato" <kuroda(dot)hayato(at)jp(dot)fujitsu(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Chris Travers <chris(dot)travers(at)adjust(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "dimitri(at)citusdata(dot)com" <dimitri(at)citusdata(dot)com> |
| Subject: | Re: Prevent extension creation in temporary schemas |
| Date: | 2019-03-01 06:16:12 |
| Message-ID: | 20190301061612.GB31098@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 28, 2019 at 10:52:52PM -0500, Tom Lane wrote:
> If you're suggesting that we disable that security restriction
> during extension creation, I really can't see how that'd be a
> good thing ...
No, I don't mean that. I was just wondering if someone can set
search_path within the SQL script which includes the extension
contents to bypass the restriction and the error. They can always
prefix such objects with pg_temp anyway if need be...
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-03-01 06:19:44 | Re: 2019-03 Starts Tomorrow |
| Previous Message | Michael Paquier | 2019-03-01 06:13:29 | Re: readdir is incorrectly implemented at Windows |