Forbid DROP SCHEMA on temporary namespaces This operation was possible for the owner of the schema or a superuser. Down to 9.4, doing this operation would cause inconsistencies in a session whose temporary schema was dropped, particularly if trying to create new temporary objects after the drop. A more annoying consequence is a crash of autovacuum on an assertion failure when logging information about an orphaned temp table dropped. Note that because of 246a6c8 (present in v11~), which has made the removal of orphaned temporary tables more aggressive, the failure could be triggered more easily, but it is possible to reproduce down to 9.4.
Reported-by: Mahendra Singh, Prabhat Sahu Author: Michael Paquier Reviewed-by: Kyotaro Horiguchi, Mahendra Singh Discussion: https://postgr.es/m/CAKYtNAr9Zq=1-ww4etho-vcc-k120yxzy5os01vkalpadbv...@mail.gmail.com Backpatch-through: 9.4 Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/f1958351eae2c9ef820825c3f50f905cff13ccaf Modified Files -------------- src/backend/commands/dropcmds.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
