pgmigrate/run_test.sh

#!/bin/sh

set -e

chown -R postgres:postgres /dist
mkdir -p /var/log/postgresql
chown postgres:postgres /var/log/postgresql
sudo -u postgres /usr/lib/postgresql/${PG_MAJOR}/bin/pg_ctl -D \
    /etc/postgresql/${PG_MAJOR}/main -l \
    /var/log/postgresql/postgresql-${PG_MAJOR}-main.log start
cd /dist
sudo -u postgres -i tox -c /dist/tox.ini
First opensource version - PGmigrate 1.0.0 2016-10-03 17:21:57 +03:00			`#!/bin/sh`

			`set -e`

			`chown -R postgres:postgres /dist`
Use application_name instead of backend pid for conflict termination. Defect was discovered by Alexander Artemenko (@svetlyak40wt). If pgmigrate is used with pgbouncer in transaction pooling mode conflict termination will fail to correctly find pgmigrate connections. In order to fix this we pass random application_name in dsn for each connection. We use LIKE-query because connection pooler could append host/port to original value. 2019-11-02 02:31:24 +03:00			`mkdir -p /var/log/postgresql`
			`chown postgres:postgres /var/log/postgresql`
Bump deps versions 2019-04-14 20:55:33 +03:00			`sudo -u postgres /usr/lib/postgresql/${PG_MAJOR}/bin/pg_ctl -D \`
			`/etc/postgresql/${PG_MAJOR}/main -l \`
Use application_name instead of backend pid for conflict termination. Defect was discovered by Alexander Artemenko (@svetlyak40wt). If pgmigrate is used with pgbouncer in transaction pooling mode conflict termination will fail to correctly find pgmigrate connections. In order to fix this we pass random application_name in dsn for each connection. We use LIKE-query because connection pooler could append host/port to original value. 2019-11-02 02:31:24 +03:00			`/var/log/postgresql/postgresql-${PG_MAJOR}-main.log start`
First opensource version - PGmigrate 1.0.0 2016-10-03 17:21:57 +03:00			`cd /dist`
			`sudo -u postgres -i tox -c /dist/tox.ini`