mirror of
https://github.com/zulip/zulip.git
synced 2026-06-30 21:11:04 +08:00
Zulip 服务器和 Web 应用程序。开源团队聊天可帮助团队保持高效和专注。
298e008cc2
Apply this commit after hours! To apply this commit, first run the migration and then run the following as the zulip user on staging: $ echo 'VACUUM zerver_message' | python manage.py dbshell The above VACUUM is needed to clean out the existing fast update pending list. It might take a long time and block new message inserts! See discussion near Zulip message 18377486 for why we're turning off the fast update mechanism for zephyr_message_search_tsvector. The high level overview is: As a consequence of the high work_mem setting on our postgres server, the fastupdate pending list for zephyr_message_search_tsvector can grow very large. This leads to the occasional INSERT or UPDATE taking inordinately long (many minutes) as the pending list is flushed, blocking other inserts. One other possible solution for preventing the list from growing too large is to set the autovacuum storage parameters on the table such that the autovacuum process will run after a reasonable number of INSERTs or UPDATEs. However, the table is mostly INSERT-only. Therefore, only the autovacuum_analyze_* parameters will actually do anything to affect when the autovacuumer will run, but when it does, it will do a VACUUM ANALYZE instead of a plain VACUUM. We don't particularly need the table to be re-analyzed that often. Turning off fast update will eventually cause the index to become less efficient, but we can always rebuild it later if we notice it starting to get too slow. (imported from commit f280c193c3bc0a3f312960510c5a7dcf97f30c3d) |
||
|---|---|---|
| analytics | ||
| api | ||
| assets | ||
| bin | ||
| bots | ||
| confirmation | ||
| corporate | ||
| humbug | ||
| node_modules | ||
| puppet | ||
| scripts | ||
| static | ||
| templates | ||
| tools | ||
| zerver | ||
| zilencer | ||
| zproject | ||
| .gitattributes | ||
| .gitignore | ||
| LICENSE | ||
| manage.py | ||
| zulip_tools.py | ||