This issue is resolved in vCenter Server 7.0 Update 3c.
Workaround:
To workaround this issue, the pg_addons extension must be manually removed from the vCenter vPostgres instance.
Warning: This procedure makes changes to the vCenter Database. VMware highly recommends contacting VMware Support to execute these steps. Ensure you have working backups or powered-off snapshots of the vCenter (or ALL vCenters if in ELM mode) before continuing.
- Connect to the vCenter vPostgres instanace
/opt/vmware/vpostgres/current/bin/psql -U postgres
- Show all of the databases which reside in vPostgres
postgres=# SELECT datname FROM pg_database WHERE datallowconn ;
datname
-----------
postgres
template1
VCDB
(3 rows)
- Connect to each database and check if the extension exists. For example,the postgres db:
postgres=# \c "postgres"
You are now connected to database "VCDB" as user "postgres".
postgres=# \dx
List of installed extensions
Name | Version | Schema | Description
-----------+---------+------------+-------------------------------------
pg_addons | 0.2 | public | Set of extra utilities for Postgres
plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language
(2 rows)
- If the extension exists in the \dx output, remove it:
postgres=# DROP EXTENSION pg_addons ;
DROP EXTENSION
- Once the db_addons extension is removed from each database, retry the upgrade