mirror of https://github.com/zulip/zulip.git
9937734e50
We have been semi-accidentally relying on the fact that terminate-psql-sessions fails silently when there are PIDs we don't have permission to terminate. This actually happens somewhat often, generally when we're doing a series of operations in quick succession by different users, because postgres processes live a little longer than the `psql` shell that started them. As part of adding ON_STOP_ERROR to all of our postgres commands, it makes sense to enforce we don't fail here, but that means we need to actually filter the target PIDs to only ones we can actually kill. Signed-off-by: Anders Kaseorg <anders@zulipchat.com> |
||
|---|---|---|
| .. | ||
| configure-rabbitmq | ||
| debathena-archive.asc | ||
| flush-memcached | ||
| generate-self-signed-cert | ||
| generate_secrets.py | ||
| initialize-database | ||
| install | ||
| packagecloud.asc | ||
| pgroonga-debian.asc | ||
| pgroonga-ppa.asc | ||
| postgres-create-db | ||
| postgres-init-db | ||
| restore-backup | ||
| setup-certbot | ||
| terminate-psql-sessions | ||
| zulip-ppa.asc | ||