fix(#3051): lock_timeout в миграции 288 — гейт CI #2752
All checks were successful
CI / changes (pull_request) Successful in 10s
CI / backend-tests (pull_request) Has been skipped
CI / openapi-codegen-check (pull_request) Has been skipped
CI Trade-In / changes (pull_request) Successful in 8s
CI Trade-In / browser-tests (pull_request) Has been skipped
CI Trade-In / frontend-checks (pull_request) Has been skipped
CI / frontend-tests (pull_request) Has been skipped
CI Trade-In / backend-tests (pull_request) Successful in 5m11s

ALTER TABLE deals ADD COLUMN без SET LOCAL lock_timeout встаёт в очередь за
чужой сессией и уводит за собой запросы приложения. Лучше упасть по таймауту
и повторить деплой.
This commit is contained in:
bot-backend 2026-09-08 22:58:38 +03:00
parent 476fb9b77a
commit e9370818ea

View file

@ -43,6 +43,10 @@
BEGIN;
-- #2752: блокирующий DDL не должен вставать в очередь за чужой сессией и уводить
-- за собой запросы приложения — лучше упасть по таймауту и повторить деплой.
SET LOCAL lock_timeout = '5s';
-- A: колонка
ALTER TABLE deals ADD COLUMN IF NOT EXISTS doc_type text;