diff options
| author | Michael Paquier <michael@paquier.xyz> | 2019-12-27 17:59:16 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2019-12-27 17:59:16 +0900 |
| commit | 786540085dbd5bccb5d8bfb9b519c4ffbf07ec28 (patch) | |
| tree | 62849d5c0e2e9c94bbca40ad5f3113500ac0e2bb /src/backend/utils/adt/tsquery_gist.c | |
| parent | ee206cb830eff45179afde06c93643210b52b196 (diff) | |
| download | postgresql-786540085dbd5bccb5d8bfb9b519c4ffbf07ec28.tar.gz postgresql-786540085dbd5bccb5d8bfb9b519c4ffbf07ec28.zip | |
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-k120YxZy5OS01VkaLPaDbv2tg@mail.gmail.com
Backpatch-through: 9.4
Diffstat (limited to 'src/backend/utils/adt/tsquery_gist.c')
0 files changed, 0 insertions, 0 deletions