Hello, Aymeric
Thanks for your reply.
CREATE INDEX CONCURRENTLY is a big part for zero downtime migrations
support, but there are too many additional questions as should ALTER TABLE
ADD COLUMN UNIQUE splitted to CREATE INDEX and constraint creation or
should be handled FOREGN KEY, CHECK and NO
Hi,
I found that django migrations don't designed for live updates on large
tables for postgres, eg. index creation doesn't use concurrently or alter
table operation can take ACCESS EXCLUSIVE lock for long time.
Before I mostly wrote custom migrations, but after one of downtime I
decided to av