Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/scripts/setup/terminate-psql-sessions

18 lines
390 B
Plaintext
Raw Normal View History

Add support for running OpenBSD in development environment.
2016-01-12 13:08:43 +01:00
#!/usr/bin/env bash
Drop database users prior to DROP/CREATE database. This fixes an annoying issue where one tries to rebuild the database, and it fails due to there being existing connections. The one thing that is potentially scary about this implementation is that it means it's now a lot easier to accidentally drop your production database by running the wrong script; might be worth adding a "--force" flag controlling this behavior or something. Thanks to Nemanja Stanarevic and Neeraj Wahi for prototypes of this implementation! They did most of the work and testing for this.
2015-09-28 19:45:35 +02:00
set -e
cd /
terminate-psql-sessions: Fix shell and SQL quoting. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
2019-01-16 04:32:27 +01:00
tables="$(printf "'%s'," "${@//\'/\'\'}")"
tables="${tables%,}"
Drop database users prior to DROP/CREATE database. This fixes an annoying issue where one tries to rebuild the database, and it fails due to there being existing connections. The one thing that is potentially scary about this implementation is that it means it's now a lot easier to accidentally drop your production database by running the wrong script; might be worth adding a "--force" flag controlling this behavior or something. Thanks to Nemanja Stanarevic and Neeraj Wahi for prototypes of this implementation! They did most of the work and testing for this.
2015-09-28 19:45:35 +02:00
terminate-psql-sessions: Rely on the caller to set PGHOST, PGUSER. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2020-06-16 01:36:02 +02:00
psql postgres -v ON_ERROR_STOP=1 <<EOF
terminate-psql-sessions: Only terminate if we have permissions. 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>
2019-04-23 23:41:42 +02:00
SELECT pg_terminate_backend(s.pid)
FROM pg_stat_activity s, pg_roles r
WHERE
s.datname IN ($tables)
AND r.rolname = CURRENT_USER
scripts: Don't terminate current session in terminate-psql-sessions. This is a prep commit. Running terminate-psql-sessions command on docker-zulip results in the script exiting with non-zero exit status 2. This is because the current session also gets terminated while running terminate-psql-sessions command. To prevent that from happening we don't terminate the session created by terminate-psql-sessions.
2020-02-26 08:34:57 +01:00
AND (s.usename = r.rolname OR r.rolsuper = 't')
AND s.pid <> pg_backend_pid();
Drop database users prior to DROP/CREATE database. This fixes an annoying issue where one tries to rebuild the database, and it fails due to there being existing connections. The one thing that is potentially scary about this implementation is that it means it's now a lot easier to accidentally drop your production database by running the wrong script; might be worth adding a "--force" flag controlling this behavior or something. Thanks to Nemanja Stanarevic and Neeraj Wahi for prototypes of this implementation! They did most of the work and testing for this.
2015-09-28 19:45:35 +02:00
EOF