| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | "Kuroda, Hayato" <kuroda(dot)hayato(at)jp(dot)fujitsu(dot)com> |
| Cc: | 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-02-19 04:35:34 |
| Message-ID: | 20190219043534.GR15532@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 18, 2019 at 05:39:09AM +0000, Kuroda, Hayato wrote:
> I seem this patch is enough, but could you explain the reason
> you drop initial proposal more detail?
> I'm not sure why extensions contained by temporary schemas are
> acceptable.
Because there are cases where they actually work. We have some of
these in core.
>> Anything depending on a temporary object will be dropped per
>> dependency links once the session is over.
>
> Extensions locate at pg_temp_* schemas are temporary objects IMO.
> How do you think? Would you implement this functionality in future?
Per the game of dependencies, extensions located in a temporary schema
would get automatically dropped at session end.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-02-19 04:38:04 | Re: Prevent extension creation in temporary schemas |
| Previous Message | Tom Lane | 2019-02-19 04:27:15 | Re: [Bug Fix] ECPG: could not use set xxx to default statement |