| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, 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: | 2020-02-28 23:21:38 |
| Message-ID: | 20200228232138.GI2688@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Fri, Feb 28, 2020 at 01:45:29PM -0500, Tom Lane wrote:
> After poking around, I see there aren't any other callers. But I think
> that the cause of this bug is clearly failure to think carefully about
> the different cases that isTempNamespaceInUse is recognizing, so that
> the right way to fix it is more like the attached.
Good idea, thanks. Your suggestion looks good to me.
> In the back branches, we could leave isTempNamespaceInUse() in place
> but unused, just in case somebody is calling it. I kind of doubt that
> anyone is, given the small usage in core, but maybe.
I doubt that there are any external callers, but I'd rather leave the
past API in place on back-branches.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-02-28 23:44:48 | Re: BUG #15858: could not stat file - over 4GB |
| Previous Message | Tomas Vondra | 2020-02-28 21:00:21 | Re: BUG #16283: crash on create index segmentation fault |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-02-28 23:24:17 | Re: Portal->commandTag as an enum |
| Previous Message | Alvaro Herrera | 2020-02-28 23:19:18 | Re: SLRU statistics |