postgresql-***.logyyyy-mm-ddThh:mm:ss,nnn UTC *** 0 VCDB vc LOG: duration: *** ms statement: BEGIN;declare "SQL_CUR***" cursor withhold for SELECT TASK_ID, NAME, DESCRIPTIONID, ENTITY_ID, ENTITY_TYPE,yyyy-mm-ddThh:mm:ss,nnn UTC *** 0 VCDB vc LOG: duration: *** ms statement: BEGIN;declare "SQL_CUR***" cursor withhold for SELECT EVENT_ID, CHAIN_ID, EVENT_TYPE, EXTENDED_CLASS, CREATE_TIME, postgresql-***.logyyyy-mm-ddThh:mm:ss,nnn UTC *** 0 LOG: Memory check: flag = rss, mem_used_bytes = *** kB, mem_avail = *** kBvpxd-profiler-***.log--> /SessionStats/SessionPool/Id='***'/Username='VSPHERE.LOCAL\vpxd-extension-***'/PropertyCollector/ComputeGUReqTime/max 0VMware vCenter Server 7.*
VMware vCenter Server 8.*
The Task and Event data stored in VCDB for a long period of time may have caused SQL execution to take a long time.
To consider deleting old task and event data by referring to the article, "Delete old tasks, events and statistics data in vCenter Server 5.x, 6.x, 7.x and 8.x.".