| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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-29 00:23:38 |
| Message-ID: | 20705.1582935818@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> 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.
Will push that, thanks for looking.
>> 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.
Agreed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juan José Santamaría Flecha | 2020-02-29 08:40:44 | Re: BUG #15858: could not stat file - over 4GB |
| Previous Message | Tom Lane | 2020-02-28 23:44:48 | Re: BUG #15858: could not stat file - over 4GB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2020-02-29 00:26:13 | Re: Portal->commandTag as an enum |
| Previous Message | Tom Lane | 2020-02-28 23:44:48 | Re: BUG #15858: could not stat file - over 4GB |