pgsql: Ensure correct lock level is used in ALTER ... RENAME
| От | Alvaro Herrera |
|---|---|
| Тема | pgsql: Ensure correct lock level is used in ALTER ... RENAME |
| Дата | |
| Msg-id | E1mcxKO-0004JX-40@gemulon.postgresql.org обсуждение исходный текст |
| Список | pgsql-committers |
Ensure correct lock level is used in ALTER ... RENAME Commit 1b5d797cd4f7 intended to relax the lock level used to rename indexes, but inadvertently allowed *any* relation to be renamed with a lowered lock level, as long as the command is spelled ALTER INDEX. That's undesirable for other relation types, so retry the operation with the higher lock if the relation turns out not to be an index. After this fix, ALTER INDEX <sometable> RENAME will require access exclusive lock, which it didn't before. Author: Nathan Bossart <bossartn@amazon.com> Author: Álvaro Herrera <alvherre@alvh.no-ip.org> Reported-by: Onder Kalaci <onderk@microsoft.com> Discussion: https://postgr.es/m/PH0PR21MB1328189E2821CDEC646F8178D8AE9@PH0PR21MB1328.namprd21.prod.outlook.com Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/3ce3fb2f7dc66fef67c8184b96245d74372b729e Modified Files -------------- src/backend/commands/tablecmds.c | 62 ++++++++++++++++++++++++------- src/test/regress/expected/alter_table.out | 48 ++++++++++++++++++++++++ src/test/regress/sql/alter_table.sql | 31 ++++++++++++++++ 3 files changed, 127 insertions(+), 14 deletions(-)
В списке pgsql-committers по дате отправления: