Quick Links

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:	Mahendra Singh <mahi6run(at)gmail(dot)com>
Cc:	PostgreSQL Hackers <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-25 08:13:37
Message-ID:	20191225081337.GH3448@paquier.xyz
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-bugs pgsql-hackers

On Wed, Dec 25, 2019 at 10:07:58AM +0530, Mahendra Singh wrote:
> Yes, you are right that we can drop temporary schema of other sessions.

I have mentioned that upthread, and basically we need to use
isAnyTempNamespace() here. My mistake.

> While applying attached patch on HEAD, I got below warnings:

The patch applies cleanly for me.
--
Michael

	From	Date	Subject
Next Message	PG Bug reporting form	2019-12-25 08:31:24	BUG #16179: is it reasonable to callback pgss_post_parse_analyze or pg_hint_plan_post_parse_analyze ???
Previous Message	Mahendra Singh	2019-12-25 04:37:58	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	Date	Subject
Next Message	Kyotaro Horiguchi	2019-12-25 08:26:30	Re: [HACKERS] WAL logging problem in 9.4.3?
Previous Message	Prabhat Sahu	2019-12-25 06:28:45	Re: Server crash with Master-Slave configuration.