From 465fb4327dab5eccdb8b88d6da5670007bd7110e Mon Sep 17 00:00:00 2001 From: href Date: Mon, 21 Jan 2019 13:10:48 +0100 Subject: [PATCH] Lock activities/users table during flake migration. --- .../20181218172826_users_and_activities_flake_id.exs | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/priv/repo/migrations/20181218172826_users_and_activities_flake_id.exs b/priv/repo/migrations/20181218172826_users_and_activities_flake_id.exs index 6e5dfaa77..39d45f7e8 100644 --- a/priv/repo/migrations/20181218172826_users_and_activities_flake_id.exs +++ b/priv/repo/migrations/20181218172826_users_and_activities_flake_id.exs @@ -15,6 +15,10 @@ defmodule Pleroma.Repo.Migrations.UsersAndActivitiesFlakeId do #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);" + # 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 users DROP CONSTRAINT users_pkey CASCADE;"