mirror of https://github.com/zulip/zulip.git
62562eedf7
If a previous attempt at an upgrade failed for some reason, the new PostgreSQL may be installed, and the conversion will succeed, but the new PostgreSQL daemon will not be running (Puppet does not force it to start). This causes the upgrade to fail when analyzing statistics, since the daemon isn't running. Explicitly start the new PostgreSQL; this does nothing in most cases, but will provider better resiliency when recovering from previous partial upgrades. |
||
|---|---|---|
| .. | ||
| apt-repos | ||
| __init__.py | ||
| compare-settings-to-template | ||
| configure-rabbitmq | ||
| create-database | ||
| create-db.sql | ||
| create-pgroonga.sql | ||
| flush-memcached | ||
| generate-rabbitmq-cookie | ||
| generate-self-signed-cert | ||
| generate_secrets.py | ||
| initialize-database | ||
| inline_email_css.py | ||
| install | ||
| reindex-textual-data | ||
| restore-backup | ||
| setup-certbot | ||
| sha256-tarball-to | ||
| terminate-psql-sessions | ||
| upgrade-postgresql | ||