Vacuum Full Job during Telco Cloud Automation upgrade

After upgrading from VMware Telco Cloud Automation 3.0.0 to 3.1.0, you need to run another Postgres job called tca-vacuum-full-db. This job does does vacuum full on all the databases and tables. This job also runs as a part of greenfield setup, but it will be mostly a no-op. Log exerpts from this job are as follows:

admin@10 [ ~ ]$ kubectl logs -n tca-mgr tca-vacuum-full-db-4pdzz 
Waiting for postgres pods 
waiting for connection to succeed... 
waiting for connection to succeed... 
waiting for connection to succeed...  
postgres cluster started... 
Running vacuum full 
INFO:  vacuuming "public.Job" 
INFO:  "Job": found 9 removable, 8246 nonremovable row versions in 1692 pages 
DETAIL:  0 dead row versions cannot be removed yet. 
CPU: user: 0.01 s, system: 0.07 s, elapsed: 0.14 s. 
... 
... 
...

A similar job can also been seen in tca-cp too in the tca-cp-cn namespace.