| From: | "Kuroda, Hayato" <kuroda(dot)hayato(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Michael Paquier' <michael(at)paquier(dot)xyz> |
| 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-18 05:39:09 |
| Message-ID: | 1F66B161998C704BABF8989B8A2AC0A31871E3@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Michael,
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.
> 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?
Hayato Kuroda
Fujitsu LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2019-02-18 05:51:10 | Re: ON SELECT rule on a table without columns |
| Previous Message | Michael Paquier | 2019-02-18 05:25:03 | Re: [Patch] checksumming-related buglets in pg_verify_checksums/pg_basebackup TAP tests |