Re: Assert failure due to "drop schema pg_temp_3 cascade" for temporary tables and \d+ is not showing any info after drooping temp table schema

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: mahi6run(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Assert failure due to "drop schema pg_temp_3 cascade" for temporary tables and \d+ is not showing any info after drooping temp table schema
Date: 2019-12-26 13:53:29
Message-ID: 20191226135329.GA249363@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Wed, Dec 25, 2019 at 12:24:10PM +0900, Michael Paquier wrote:
> Arf. Yes, this had better be isAnyTempNamespace() so as we complain
> about all of them.

Okay, finally coming back to that. Attached is an updated patch with
polished comments and the fixed logic.
--
Michael

Attachment Content-Type Size
drop-temp-schema-v2.patch text/x-diff 1.1 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mahendra Singh 2019-12-26 14:50:14 Re: Assert failure due to "drop schema pg_temp_3 cascade" for temporary tables and \d+ is not showing any info after drooping temp table schema
Previous Message Amit Langote 2019-12-26 08:00:34 Re: A row-level trigger on a partitioned table is not created on a sub-partition created later

Browse pgsql-hackers by date

  From Date Subject
Next Message Anastasia Lubennikova 2019-12-26 14:45:19 Re: standby recovery fails (tablespace related) (tentative patch and discussion)
Previous Message Alexey Kondratov 2019-12-26 13:35:31 Re: Physical replication slot advance is not persistent