Re: Autovaccuum vs temp tables crash - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Autovaccuum vs temp tables crash
Date
Msg-id 20190223151846.GE8725@paquier.xyz
Whole thread Raw
In response to Re: Autovaccuum vs temp tables crash  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Autovaccuum vs temp tables crash
List 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

Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: FOP warnings about id attributes in title tags
Next
From: Magnus Hagander
Date:
Subject: Re: Autovaccuum vs temp tables crash