|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|Cc:||Amul Sul <sulamul(at)gmail(dot)com>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Skip temporary table schema name from explain-verbose output.|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Oh, you meant this one. To be honest I don't remember *why* this code
> wants to show remote temp tables as just "pg_temp" ... it's possible
> that some test in the DDL-to-JSON code depended on this behavior.
> Without spending too much time analyzing it, I agree that it seems
> dangerous and might lead to referring to unintended objects. (Really,
> my memory is not clear on *why* we would be referring to temp tables of
> other sessions.)
Yeah, it's not very clear why that would happen, but if it does,
showing "pg_temp" seems pretty misleading. I tried replacing the
code with just get_namespace_name_or_temp(), and it still gets
through check-world, for whatever that's worth.
I'm inclined to change this in HEAD but leave it alone in the back
branches. While it seems pretty bogus, it's not clear if anyone
out there could be relying on the current behavior.
regards, tom lane
|Next Message||Robert Haas||2021-07-26 19:09:07||Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers)|
|Previous Message||Arne Roland||2021-07-26 18:11:28||Re: Rename of triggers for partitioned tables|