| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Autovaccuum vs temp tables crash |
| Date: | 2019-02-23 15:18:46 |
| Message-ID: | 20190223151846.GE8725@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Feb 23, 2019 at 02:48:58PM +0100, Magnus Hagander wrote:
> I think we need to either prevent dropping of temp namespaces *or* we need
> to create a new entry in pg_namespace in this particular case.
Perhaps I am missing something, but it would be just more simple to
now allow users to restrict that?
> I wonder if other "fun" things could happen if you go rename the namespace,
> haven't tried that yet...
In this case the OID remains the same, still there are some cases
where we rely on the namespace name, and one is CLUSTER.
objectaddress.c uses as well get_namespace_name_or_temp(), which would
be messed up, so it would be better to prevent a temp namespace to be
renamed. Could ALTER SCHEMA OWNER TO also be a problem?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2019-02-23 15:28:15 | Re: Autovaccuum vs temp tables crash |
| Previous Message | Andrew Dunstan | 2019-02-23 14:47:54 | Re: FOP warnings about id attributes in title tags |