The best option for the password is to lower security so it’s not required to enter a password when you log into postgres
Day to day we have to delete duplicate data from the database.
An upgrade requires Primary key where one didn’t exist before or a db let it guard down and didn’t enforce the PK’s (yeah looking at you postgres!)
Or if an upgrade can’t create a new pk then this is useful. The SQL Server commands to find this are there too.
The easiest way to see the interactions that are going from vc to the database then you can increase logging to see these sql statements.
If a vm is being highlighted in the vpxd logs and the reason for vc to crash then it’s always useful to remove this vm from the database to see if it will allow vc to startup.
If postgres replication is broken you may as well reset it up as opposed to trying to manually move the logs. Here’s how to do it
su – postgres /opt/vmware/vpostgres/current/bin/psql -d vcopsdb -p 5433