An INSERT may run much longer than expected and appear to request an extremely large memory budget. Investigation shows the large “reported” memory requirement is driven by resource pool policy/configuration (runtime caps and pool routing), not actual memory usage. When the query exceeds the configured runtime cap, Vertica can move it from a short-running pool to a long-running pool, which changes how it is managed and can contribute to the observed slowdown.
Environment
Vertica Analytics database 24.3.x
Situation
-
INSERT takes much longer than baseline (minutes → hours).
-
Monitoring/plan output shows a very large reported memory requirement or budget.
-
Query is moved/reclassified due to runtime cap exceeded.
-
Actual memory usage is significantly lower than the reported budget.
