mirror of https://github.com/zulip/zulip.git
a1aae4a39f
We accidentally lost this when we did the User/UserProfile merge (this commit also deletes the old code to add the auth_user index in do-destroy-rebuild-database). This below is mostly just notes for future reference, but when deploying this change to staging, we should consider running the following instead of using the migration directly: CREATE UNIQUE INDEX CONCURRENTLY zephyr_userprofile_email_uniq ON zephyr_userprofile(email); ALTER TABLE zephyr_userprofile ADD CONSTRAINT zephyr_userprofile_email_uniq UNIQUE USING INDEX zephyr_userprofile_email_uniq; CREATE INDEX CONCURRENTLY zephyr_userprofile_email ON zephyr_userprofile(email); But I think it might be the case that it's fine to just run it directly, since the ALTER TABLE part seems to hang if there's an open transaction working on a UserProfile object anyway. (imported from commit 1bf34ce242de51e97c91c8bab86b6b273e17fb43) |
||
---|---|---|
.. | ||
humbug_tools | ||
inject-messages | ||
jslint | ||
print-all | ||
build-api-tarball | ||
check-all | ||
clean-branches | ||
clean-repo | ||
deploy-branch | ||
django-command-line | ||
django-template-graph | ||
do-destroy-rebuild-database | ||
merge-messages-logs | ||
msmtprc.example | ||
munge_postgres_logs.pl | ||
node | ||
post-receive | ||
postgres-init-db | ||
process-user-activity-command-line | ||
restart-server | ||
review | ||
run-dev.py | ||
test-all | ||
test-backend | ||
tornado-command-line | ||
update-deployment | ||
update-prod-static |