| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Mahendra Singh <mahi6run(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-01-08 00:44:09 |
| Message-ID: | 20200108004409.GA3413@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Tue, Jan 07, 2020 at 01:06:08PM -0500, Tom Lane wrote:
> I still agree with Robert that a052f6c is a bad idea. It's not the case
> that that's blocking "any connected user" from causing an issue. The
> temp schemas are always owned by the bootstrap superuser, so only a
> superuser could delete them. All that that patch is doing is preventing
> superusers from doing something that they could reasonably wish to do,
> and that is perfectly safe when there's not concurrent usage of the
> schema. We are not normally that nanny-ish, and the case for being so
> here seems pretty thin.
Okay, I am running out of arguments then, so attached is a patch to
address things. I would also prefer if we keep the relation name in
the log even if the namespace is missing.
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| drop-temp-schema-adjust-v2.patch | text/x-diff | 2.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-08 00:55:17 | 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 | PG Bug reporting form | 2020-01-08 00:03:51 | BUG #16196: RPM package for PG 10.11 assumes that all Centos >= 7 use python2-libs, but 7.4 doesn't |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-08 00:55:17 | 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 | Tom Lane | 2020-01-08 00:42:48 | Re: xact_start for walsender & logical decoding not updated |