Knowing those two facts, we can calculate catalog memory usage on all nodes by querying the system table RESOURCE_POOL_STATUS for the METADATA pool!
Example:
dbadmin=> SELECT node_name, pool_name, memory_size_kb/1024^2 AS memory_size_kb_gb
dbadmin-> FROM resource_pool_status
dbadmin-> WHERE pool_name = 'metadata';
node_name | pool_name | memory_size_kb_gb
--------------------+-----------+-------------------
v_test_db_node0001 | metadata | 0.104231834411621
v_test_db_node0002 | metadata | 0.104231824231921
v_test_db_node0003 | metadata | 0.104231834213117
(1 row)
Helpful Links:https://www.vertica.com/docs/latest/HTML/Content/Authoring/SQLReferenceManual/SystemTables/MONITOR/RESOURCE_POOL_STATUS.htm
https://www.vertica.com/docs/latest/HTML/Content/Authoring/SQLReferenceManual/Statements/Built-inPools.htm
Have fun!
About the Author
James Knicely
Vertica Field Chief Technologist
I've had the privilege of working with many database technologies in my career. But after being introduced to Vertica in May of 2011 as a client, I was hooked on the new technology after witnessing a query run in milliseconds that had previously ran for hours on the legacy database we had in place. It was then that I knew I wanted to eventually join the Vertica team, and 4 years later I did! I am currently a Vertica evangelist and am ready to help you get on board! Please feel free to reach out to me with any questions you have about Vertica and make sure to follow my Vertica Quick Tips!
