From aaad7fe2f7d90a7f20ec794b374855f72c2dc155 Mon Sep 17 00:00:00 2001 From: Sampriti Panda Date: Thu, 31 May 2018 06:05:48 +0530 Subject: [PATCH] pgroonga: Remove long-running update query in initial migration. This query doesn't add any value, because it'll be overwritten in migration 0002 anyway. And because it isn't batched, it can take several minutes to run on servers with hundreds of thousands to millions of messages of history. During that time, it's in a transaction, and thus one can't send messages, so it forces downtime. --- pgroonga/migrations/0001_enable.py | 2 -- 1 file changed, 2 deletions(-) diff --git a/pgroonga/migrations/0001_enable.py b/pgroonga/migrations/0001_enable.py index 282db08732..bb9bec3283 100644 --- a/pgroonga/migrations/0001_enable.py +++ b/pgroonga/migrations/0001_enable.py @@ -20,8 +20,6 @@ SET search_path = %(SCHEMA)s,public,pgroonga,pg_catalog; ALTER TABLE zerver_message ADD COLUMN search_pgroonga text; -UPDATE zerver_message SET search_pgroonga = subject || ' ' || rendered_content; - -- TODO: We want to use CREATE INDEX CONCURRENTLY but it can't be used in -- transaction. Django uses transaction implicitly. -- Django 1.10 may solve the problem.