Cannot upgrade chart to 3.3.13

Summary

Cannot upgrade chart from 3.3.12 to 3.3.13

Steps to reproduce

Change chart version and apply

Current behavior

The migration container fails

Expected behavior

Normal upgrade

Versions

  • Chart: 3.3.12

  • Platform:

    • Cloud: GKE

  • Kubernetes:

    • Client: 1.15.0
    • Server: 1.15.11

  • Helm: (helm version)

    • Client: 3.1.2
    • Server: 3.1.2

  • Postgres:

    • chart: 7.7.3
    • Version: 10.9

Relevant logs

Logs from gitlab-migrations

Begin parsing .erb files from /var/opt/gitlab/templates
Writing /srv/gitlab/config/cable.yml
Writing /srv/gitlab/config/database.yml
Writing /srv/gitlab/config/resque.yml
Writing /srv/gitlab/config/gitlab.yml
Copying other config files found in /var/opt/gitlab/templates
Attempting to run '/scripts/wait-for-deps /scripts/db-migrate' as a main process
Checking database connection and schema version
/srv/gitlab/vendor/bundle/ruby/2.6.0/bin/rake db:version: symbol lookup error: /srv/gitlab/vendor/bundle/ruby/2.6.0/gems/pg-1.2.2/lib/pg_ext.so: undefined symbol: PQresultMemorySize
Checking database connection and schema version
/srv/gitlab/vendor/bundle/ruby/2.6.0/bin/rake db:version: symbol lookup error: /srv/gitlab/vendor/bundle/ruby/2.6.0/gems/pg-1.2.2/lib/pg_ext.so: undefined symbol: PQresultMemorySize
Checking database connection and schema version
/srv/gitlab/vendor/bundle/ruby/2.6.0/bin/rake db:version: symbol lookup error: /srv/gitlab/vendor/bundle/ruby/2.6.0/gems/pg-1.2.2/lib/pg_ext.so: undefined symbol: PQresultMemorySize
Checking database connection and schema version
/srv/gitlab/vendor/bundle/ruby/2.6.0/bin/rake db:version: symbol lookup error: /srv/gitlab/vendor/bundle/ruby/2.6.0/gems/pg-1.2.2/lib/pg_ext.so: undefined symbol: PQresultMemorySize
Checking database connection and schema version
/srv/gitlab/vendor/bundle/ruby/2.6.0/bin/rake db:version: symbol lookup error: /srv/gitlab/vendor/bundle/ruby/2.6.0/gems/pg-1.2.2/lib/pg_ext.so: undefined symbol: PQresultMemorySize
WARNING: Waiting for all services to be operational, and data migrations to complete.
If this container continues to fail / restart, please see:
  https://docs.gitlab.com/charts/troubleshooting/index.html#application-containers-constantly-initializing

The same error is present in the unicorn container