• Michael Paquier's avatar
    Forbid DROP SCHEMA on temporary namespaces · a052f6cb
    Michael Paquier authored
    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 246a6c8f (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-k120YxZy5OS01VkaLPaDbv2tg@mail.gmail.com
    Backpatch-through: 9.4
    a052f6cb
dropcmds.c 15.9 KB