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
To backup the postgres database manually on windows
If your concerned your SQL server database is the cause of a performance issue then these commands might help