harbor/make/photon/db/docker-entrypoint.sh
Yang Jiao b44c9d01dd
Drop build postgresql 9.6 (#17458)
Drop pg9.6, will not support upgrading from pg9.6 to pg13, if you use pg9.6 you can upgrade to 2.5 and upgrade to 2.7

Signed-off-by: Yang Jiao <jiaoya@vmware.com>
2022-09-21 17:59:25 +08:00

72 lines
3.2 KiB
Bash
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

#!/bin/bash
set -e
source $PWD/initdb.sh
CUR=$PWD
PG_VERSION_OLD=$1
PG_VERSION_NEW=$2
PGBINOLD="/usr/pgsql/${PG_VERSION_OLD}/bin"
PGDATAOLD=${PGDATA}/pg${PG_VERSION_OLD}
PGDATANEW=${PGDATA}/pg${PG_VERSION_NEW}
# We should block the upgrade path from 9.6 directly.
if [ -s $PGDATA/PG_VERSION ]; then
echo "Upgrading from PostgreSQL 9.6 to PostgreSQL $PG_VERSION_NEW is not supported in the current Harbor release."
echo "You should upgrade to previous Harbor firstly, then upgrade to current release."
exit 1
fi
# Upgrade DB: 1. PG_NEW\PG_VERSION file doesnt exist and pg_old_parameter is not nil and PG_OLD\PG_VERSION file exist.
# For example: ["13", "14"]
# In harbor v2.8, Harbor 2.7 was installed before, db version was 13,
# It needs to upgrade the database from pg 13 to pg 14,
# ["13", "14"] means support for upgrading from pg 13 to pg 14.
# Init DB: 1. PG_NEW\PG_VERSION file doesnt exist and pg_old_parameter is not nil and PG_OLD\PG_VERSION file doesnt exist.
# For example: ["13", "14"]
# In harbor v2.8, the first time installation, it needs to init the db for pg 14,
# ["13", "14"] means support for upgrading from pg 13 to pg 14.
# 2. PG_NEW\PG_VERSION file doesnt exist and pg_old_parameter is nil.
# For example: ["", "14"]
# In harbor v2.8, the first time installation, it needs to init the db for pg 14,
# ["", "14"] means db upgrade is not supported.
if [ ! -s $PGDATANEW/PG_VERSION ]; then
if [ ! -z $PG_VERSION_OLD ] && [ -s $PGDATAOLD/PG_VERSION ]; then
echo "upgrade DB from $PG_VERSION_OLD to $PG_VERSION_NEW"
initPG $PGDATANEW false
set +e
# In some cases, like helm upgrade, the postgresql may not quit cleanly.
# Use start & stop to clean the unexpected status. Error:
# There seems to be a postmaster servicing the new cluster.
# Please shutdown that postmaster and try again.
# Failure, exiting
$PGBINOLD/pg_ctl -D "$PGDATAOLD" -w -o "-p 5433" start
$PGBINOLD/pg_ctl -D "$PGDATAOLD" -m fast -w stop
./$CUR/upgrade.sh --old-bindir $PGBINOLD --old-datadir $PGDATAOLD --new-datadir $PGDATANEW
# it needs to clean the $PGDATANEW on upgrade failure
if [ $? -ne 0 ]; then
echo "remove the $PGDATANEW after fail to upgrade."
rm -rf $PGDATANEW
exit 1
fi
set -e
echo "remove the $PGDATAOLD after upgrade success."
rm -rf $PGDATAOLD
else
echo "init DB, DB version:$PG_VERSION_NEW"
initPG $PGDATANEW true
fi
fi
POSTGRES_PARAMETER=''
file_env 'POSTGRES_MAX_CONNECTIONS' '1024'
# The max value of 'max_connections' is 262143
if [ $POSTGRES_MAX_CONNECTIONS -le 0 ] || [ $POSTGRES_MAX_CONNECTIONS -gt 262143 ]; then
POSTGRES_MAX_CONNECTIONS=262143
fi
POSTGRES_PARAMETER="${POSTGRES_PARAMETER} -c max_connections=${POSTGRES_MAX_CONNECTIONS}"
exec postgres -D $PGDATANEW $POSTGRES_PARAMETER