mirror of https://github.com/zulip/zulip.git
0d7dbd1b07
Running `pg-upgradecluster` runs the `CREATE TEXT SEARCH DICTIONARY` and `CREATE TEXT SEARCH CONFIGURATION` from `zerver/migrations/0001_initial.py` on the new PostgreSQL cluster; this requires that the stopwords file and dictionary exist _prior_ to `pg_upgradecluster` being run. This causes a minor dependency conflict -- we do not wish to duplicate the functionality from `zulip::postgres_appdb_base` which configures those files, but installing all of `zulip::postgres_appdb_tuned` will attempt to restart PostgreSQL -- which has not configured the cluster for the new version yet. In order to split out configuration of the prerequisites for the application database, and the steps required to run it, we need to be able to apply only part of the puppet configuration. Use the newly-added `--config` argument to provide a more limited `zulip.conf` which only applies `zulip::postgres_appdb_base` to the new version of Postgres, creating the required tsearch data files. This also preserves the property that a failure at any point prior to the `pg_upgradecluster` is easily recoverable, by re-running `zulip-puppet-apply`. |
||
|---|---|---|
| .. | ||
| authentication-methods.md | ||
| deployment.md | ||
| email-gateway.md | ||
| email.md | ||
| expensive-migrations.md | ||
| export-and-import.md | ||
| index.rst | ||
| install-existing-server.md | ||
| install.md | ||
| maintain-secure-upgrade.md | ||
| management-commands.md | ||
| mobile-push-notifications.md | ||
| multiple-organizations.md | ||
| password-strength.md | ||
| postgres.md | ||
| requirements.md | ||
| security-model.md | ||
| settings.md | ||
| ssl-certificates.md | ||
| troubleshooting.md | ||
| upgrade-or-modify.md | ||
| upload-backends.md | ||
| zoom-configuration.md | ||