mirror of
https://github.com/zulip/zulip.git
synced 2026-06-27 21:01:32 +08:00
2057057be4
This can happen if `machine.pgroonga` is set during initial installation. We cannot run `CREATE EXTENSION PGROONGA` because the database that we need to run that statement in does not exist yet; make the command a silent no-op that does not create the `pgroonga_setup.sql.applied` flag file, such that a later `zulip-puppet-apply` once the database exists can pick up and install the extension. |
||
|---|---|---|
| .. | ||
| apt-repos | ||
| __init__.py | ||
| compare-settings-to-template | ||
| configure-rabbitmq | ||
| create-database | ||
| create-db.sql | ||
| create-pgroonga.sql | ||
| flush-memcached | ||
| generate_secrets.py | ||
| generate-rabbitmq-cookie | ||
| generate-self-signed-cert | ||
| initialize-database | ||
| install | ||
| pgroonga-config | ||
| reindex-textual-data | ||
| restore-backup | ||
| setup-certbot | ||
| sha256-file-to | ||
| sha256-tarball-to | ||
| terminate-psql-sessions | ||
| upgrade-postgresql | ||