EXECUTION_ENGINE_PROFILES data only stays for a split second
I'm not sure if I missed to enable something, but how come after running PROFILE , the data in table EXECUTION_ENGINE_PROFILES only stays for a couple of seconds?
0
I'm not sure if I missed to enable something, but how come after running PROFILE , the data in table EXECUTION_ENGINE_PROFILES only stays for a couple of seconds?
Comments
Maybe check dc_execution_engine_profiles?
I concur with Jim. The system tables are non persistent and depending on the number of users and complexity of queries things can roll off pretty quickly. The DC (data_collector) tables are a persistent version of many of the key system tables. They have configurable retention policies that allow you to modify how much info they store on either a memory/disk space and/or time based value.
A good reference in the documentation is in the Administrator's Guide > Monitoring Vertica > Retaining Monitoring Information
Also check
SELECT get_data_collector_policy('ExecutionEngineProfiles');
to see if there is a retention policy.
The records didn't go to dc_execution_engine_profiles.
I reran the profile and captured the records in v_monitor.execution_engine_profiles while the query was still running.
oh no! I just realized the values in (v_monitor.execution_engine_profiles) are changing as the query is running. Where can I get the final values?