On the TemBoard server (version 9.0.1) (server OS: RHEL8.9, PostgreSQL: v15.6), we have 78 times of this error within 2.5 hours, with the same DETAIL about 'in memory context "TopTransactionContext"', but the table name in schema 'temboard' that involved in the 'automatic vacuum' is different.
Error messages in the PostgreSQL log:
ERROR: out of memory
DETAIL: Failed on request of size 1xxxxxxxxx in memory context "TopTransactionContext".
2026-03-02 08:06:14 CST [3074809]: [6-1] user=,db=,app=,client= CONTEXT: automatic vacuum of table "temboard.statements.statements_history_current"
2026-03-02 08:06:14 CST [3074809]: [7-1] user=,db=,app=,client= LOG: automatic vacuum of table "temboard.pg_toast.pg_toast_502705": index scans: 1
Is there any solution to fix these errors?
On the TemBoard server (version 9.0.1) (server OS: RHEL8.9, PostgreSQL: v15.6), we have 78 times of this error within 2.5 hours, with the same DETAIL about 'in memory context "TopTransactionContext"', but the table name in schema 'temboard' that involved in the 'automatic vacuum' is different.
Error messages in the PostgreSQL log:
ERROR: out of memory
DETAIL: Failed on request of size 1xxxxxxxxx in memory context "TopTransactionContext".
2026-03-02 08:06:14 CST [3074809]: [6-1] user=,db=,app=,client= CONTEXT: automatic vacuum of table "temboard.statements.statements_history_current"
2026-03-02 08:06:14 CST [3074809]: [7-1] user=,db=,app=,client= LOG: automatic vacuum of table "temboard.pg_toast.pg_toast_502705": index scans: 1
Is there any solution to fix these errors?