Canceling query because of high VMEM usage

[thomastsang84]

### Ask for your help and thanks.
I was using navicat to view table structure and it poped up a error dialog as below:

I tried to repeat the problem server times and found out that the error dialog will be poped up after I viewed 3+ table structures.
The used memory of the active master server will be soared from 4G+ to 11G+:

I used gplogfilter to locate error messages and it shows error messages as below:
2025-03-12 22:10:26.611116 CST|gxpt_ysj|gxpt_ysj|p90739|th1818354368|10.14.218.180|62285|2025-03-12 22:09:23 CST|0|con3997|cmd125|seg-1||||sx1|ERROR: |XX000|Canceling query because of high VMEM usage. Used: 3551MB, available 819MB, red zone: 7372MB (runaway_cleaner.c:191)||||||SELECT DISTINCT CASE WHEN rcl.oid >0 THEN rcl.relkind WHEN con.oid >0 THEN con.contype WHEN tg.oid >0 THEN 'g' WHEN typ.oid >0 THEN 'T' WHEN pro.oid >0 THEN 'o' WHEN opc.oid >0 THEN 'l' WHEN opr.oid >0 THEN 'e' WHEN conv.oid >0 THEN 'n' WHEN cas.oid >0 THEN 'a' WHEN opf.oid >0 THEN 'y' WHEN amopr.oid >0 THEN 'e' WHEN amproc.oid >0 THEN 'o' WHEN usrm.umid >0 THEN 'U' WHEN fs.oid >0 THEN 'F' WHEN ft.ftrelid >0 THEN 'f' WHEN cl.relkind IS NOT NULL THEN cl.relkind ELSE ' ' END AS objtype, COALESCE(r.ev_class, d.objid) AS objid, COALESCE(rcl.relname, typ.typname, con.conname, cl.relname, pro.proname, tg.tgname, conv.conname, cstyp.typname||'->'||cttyp.typname, opc.opcname, opr.oprname, opf.opfname, amopr.oprname, amproc.amproc::text, pg_get_userbyid(usrm.umuser)) AS depname, COALESCE(rcl.relnamespace, typ.typnamespace, con.connamespace, cl.relnamespace, pro.pronamespace, conv.connamespace, opc.opcnamespace, opr.oprnamespace, opf.opfnamespace, amopr.oprnamespace) AS depnamespace, d.deptype, con.oid AS conoid FROM pg_depend d LEFT JOIN pg_class c ON c.oid = d.classid LEFT JOIN pg_class cl ON cl.oid = d.objid LEFT JOIN pg_rewrite r ON r.oid = d.objid LEFT JOIN pg_class rcl ON rcl.oid = r.ev_class LEFT JOIN pg_type typ ON typ.oid = d.objid LEFT JOIN pg_constraint con ON con.oid = d.objid LEFT JOIN pg_proc pro ON pro.oid = d.objid LEFT JOIN pg_trigger tg ON tg.oid = d.objid LEFT JOIN pg_conversion conv ON conv.oid = d.objid LEFT JOIN pg_cast cas ON cas.oid = d.objid LEFT JOIN pg_type cstyp ON cstyp.oid = cas.castsource LEFT JOIN pg_type cttyp ON cttyp.oid = cas.casttarget LEFT JOIN pg_opclass opc ON opc.oid = d.objid LEFT JOIN pg_operator opr ON opr.oid = d.objid LEFT JOIN pg_opfamily opf ON opf.oid = d.objid LEFT JOIN pg_amop amop ON amop.oid = d.objid LEFT JOIN pg_operator amopr ON amopr.oid = amop.amopopr LEFT JOIN pg_amproc amproc ON amproc.oid = d.objid LEFT JOIN pg_user_mappings usrm ON usrm.umid = d.objid LEFT JOIN pg_foreign_server fs ON fs.oid = d.objid LEFT JOIN pg_foreign_table ft ON ft.ftrelid = d.objid WHERE c.relname <> 'pg_attrdef' AND d.refobjid = 4565305::OID AND (r.oid IS NULL OR r.ev_class <> 4565305::OID)|0||runaway_cleaner.c|191|Stack trace:
1 0x7fb06b5aa426 libpostgres.so errstart + 0x206
2 0x7fb06b5ed02c libpostgres.so RunawayCleaner_StartCleanup + 0xfc
3 0x7fb06b37adb9 libpostgres.so add_path + 0x79
4 0x7fb06b33e500 libpostgres.so + 0x6b33e500
5 0x7fb06b33fa0f libpostgres.so add_paths_to_joinrel + 0x112f
6 0x7fb06b34180f libpostgres.so + 0x6b34180f
7 0x7fb06b34218e libpostgres.so make_join_rel + 0x12e
8 0x7fb06b342574 libpostgres.so join_search_one_level + 0x124
9 0x7fb06b32b743 libpostgres.so standard_join_search + 0x53
10 0x7fb06b32b88e libpostgres.so + 0x6b32b88e
11 0x7fb06b32bbd6 libpostgres.so make_one_rel + 0x256
12 0x7fb06b354856 libpostgres.so query_planner + 0x156
13 0x7fb06b35b102 libpostgres.so + 0x6b35b102
14 0x7fb06b35d825 libpostgres.so subquery_planner + 0xb35
15 0x7fb06b35dedb libpostgres.so standard_planner + 0x1cb
16 0x7fb06b35eabd libpostgres.so planner + 0x15d
17 0x7fb06b451461 libpostgres.so pg_plan_query + 0x21
18 0x7fb06b451563 libpostgres.so pg_plan_queries + 0x53
19 0x7fb06b451a8e libpostgres.so exec_simple_query + 0x48e
20 0x7fb06b456257 libpostgres.so PostgresMain + 0x23e7
21 0x7fb06b3b1ddf libpostgres.so + 0x6b3b1ddf
22 0x7fb06b3b2f1f libpostgres.so PostmasterMain + 0xeaf
23 0x4017ae postgres main + 0x57e
24 0x7fb06a502873 libc.so.6 __libc_start_main + 0xf3
25 0x40194e postgres _start + 0x2e

[thomastsang84]

I found that there was only one segment instance on each of segment servers. I expanded to 4 and It seems that the error dialog won't be poped up again.

[tuhaihe]

Cool. Since this was resolved, close this discussion.