Re: PostgreSQL 14.4 ERROR: out of memory issues - Mailing list pgsql-general
From | Pavel Stehule |
---|---|
Subject | Re: PostgreSQL 14.4 ERROR: out of memory issues |
Date | |
Msg-id | CAFj8pRBtWWU3N4xgYWjqA3p4VffAEF9kp+CWWskNo5BwhA5BEQ@mail.gmail.com Whole thread Raw |
In response to | PostgreSQL 14.4 ERROR: out of memory issues (Aleš Zelený <zeleny.ales@gmail.com>) |
Responses |
Re: PostgreSQL 14.4 ERROR: out of memory issues
|
List | pgsql-general |
Hi
It's looks like memory leak
ErrorContext: 8192 total in 1 blocks; 7928 free (5 chunks); 264 used
Grand total: 1456224 bytes in 195 blocks; 378824 free (165 chunks); 1077400 used
2022-07-02 14:48:07 CEST [3930]: [3-1] user=,db=,host=,app= ERROR: out of memory
2022-07-02 14:48:07 CEST [3930]: [4-1] user=,db=,host=,app= DETAIL: Failed on request of size 152094068 in memory context "TopTransactionContext".
2022-07-02 14:48:07 CEST [3930]: [5-1] user=,db=,host=,app= CONTEXT: automatic vacuum of table "prematch.replication.tab_queue_tmp"
2022-07-02 14:48:47 CEST [4476]: [42-1] user=,db=,host=,app= LOG: could not fork worker process: Cannot allocate memory
2022-07-02 14:48:47 CEST [4476]: [43-1] user=,db=,host=,app= LOG: could not fork worker process: Cannot allocate memory
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
2022-07-02 14:48:47 CEST [4476]: [44-1] user=,db=,host=,app= LOG: background worker "parallel worker" (PID 4303) was terminated by signal 6: Aborted
But what you see is probably just side effect. Do you use some extension in C++? This is C++ message. This process kills Postgres.
It can be related to some operation over prematch.replication.tab_queue_tmp because in both cases an atovacuum was started.
132 hba parser context: 25600 total in 6 blocks; 4464 free (8 chunks); 21136 used
133 ErrorContext: 8192 total in 1 blocks; 7928 free (5 chunks); 264 used
134Grand total: 1456224 bytes in 195 blocks; 378824 free (165 chunks); 1077400 used
1352022-07-02 14:48:07 CEST [3930]: [3-1] user=,db=,host=,app= ERROR: out of memory
1362022-07-02 14:48:07 CEST [3930]: [4-1] user=,db=,host=,app= DETAIL: Failed on request of size 152094068 in memory context "TopTransactionContext".
1372022-07-02 14:48:07 CEST [3930]: [5-1] user=,db=,host=,app= CONTEXT: automatic vacuum of table "prematch.replication.tab_queue_tmp"
I am not sure, but it looks like corrupted table prematch.replication.tab_queue_tmp
And a few days later again:2022-07-08 14:54:22 CEST [4791]: [81186-1] user=app_evaluation,db=prematch,host=172.25.0.80,app=Evaluation_STS_UAT DETAIL: parameters: $1 = '1', $2 = '1748010445', $3 = '0', $4 = '1000' terminate called after throwing an instance of 'std::bad_alloc' terminate called after throwing an instance of 'std::bad_alloc' what(): what(): std::bad_allocstd::bad_alloc 2022-07-08 14:54:23 CEST [4476]: [49-1] user=,db=,host=,app= LOG: background worker "parallel worker" (PID 25251) was terminated by signal 6: Aborted2022-07-08 14:54:23 CEST [4476]: [51-1] user=,db=,host=,app= LOG: terminating any other active server processesThanks Ales Zeleny
pgsql-general by date: