Lock activities/users table during flake migration.
This commit is contained in:
parent
973c9eed18
commit
465fb4327d
1 changed files with 4 additions and 0 deletions
|
@ -15,6 +15,10 @@ def change do
|
||||||
#execute "update activities set external_id = CAST( LPAD( TO_HEX(id), 32, '0' ) AS uuid);"
|
#execute "update activities set external_id = CAST( LPAD( TO_HEX(id), 32, '0' ) AS uuid);"
|
||||||
#execute "update users set external_id = CAST( LPAD( TO_HEX(id), 32, '0' ) AS uuid);"
|
#execute "update users set external_id = CAST( LPAD( TO_HEX(id), 32, '0' ) AS uuid);"
|
||||||
|
|
||||||
|
# Lock both tables to avoid a running server to meddling with our transaction
|
||||||
|
execute "LOCK TABLE activities;"
|
||||||
|
execute "LOCK TABLE users;"
|
||||||
|
|
||||||
execute "ALTER TABLE activities DROP CONSTRAINT activities_pkey CASCADE;"
|
execute "ALTER TABLE activities DROP CONSTRAINT activities_pkey CASCADE;"
|
||||||
execute "ALTER TABLE users DROP CONSTRAINT users_pkey CASCADE;"
|
execute "ALTER TABLE users DROP CONSTRAINT users_pkey CASCADE;"
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue