Skip to main content
Question

How to increase Database memory usage?

  • May 20, 2026
  • 2 replies
  • 7 views

joergschaber
Forum|alt.badge.img+2

Hi,

yesterday we updated our Vertica database from 26.1.0-2 to 26.2.0. After the update the observed a significant loss of database performance, i.e. queries run extremely slow, affecting critically our business.
Analysing the issue, we observe a drastic drop in memory usage, from 37% to 4%. From our side there were no changes in terms of resource pools or general database usage.
Any idea what the reason might be? Can we increase the memory usage again?

Regards,
Jörg

2 replies

mosheg
Forum|alt.badge.img+2
  • Participating Frequently
  • May 20, 2026

My strongest suspicion would be one of the following:

  • MAXQUERYMEMORYSIZE or MAXMEMORYSIZE changed
  • PLANNEDCONCURRENCY increased
  • The effective memory available to the GENERAL pool was reduced
  • Metadata/catalog memory is now reducing the memory available to GENERAL
  • Maybe some queries are spilling because memory grants are too small

For an urgent production issue, I would recommend opening a support ticket and including the following outputs:
SELECT version();

SELECT *
FROM resource_pools
ORDER BY name;

SELECT *
FROM resource_pool_status
ORDER BY node_name, pool_name;

SELECT *
FROM configuration_parameters
WHERE parameter_name ILIKE '%memory%'
OR parameter_name ILIKE '%metadata%';

If available, also include the EXPLAIN plan and qprof output for one affected slow query, ideally from both before and after the upgrade. This should help determine whether the performance degradation is caused by resource-pool or memory-grant changes, or by a different optimizer plan after the upgrade.


joergschaber
Forum|alt.badge.img+2
  • Author
  • Participating Frequently
  • May 21, 2026

Hi Mosheh,

thanks for your swift reply!
The seemed to be a problem with an anitvuris program that scanned the catalog/data/depot/temp directories which slowed down the system.
We implemented an exempt from the AV scan. That helped.
Not sure what that had to do with the new version maybe it had to do with a new system patch that we applied.
However, maybe that helps others as well.