| From: | Mladen Gogala <gogala(dot)mladen(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL Out of Memory |
| Date: | 2022-09-05 15:25:55 |
| Message-ID: | eab6a451-f181-c179-b423-6e63753aeddb@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 9/5/22 07:54, liam saffioti wrote:
> Hi Teams,
>
> FATAL: terminating background worker "parallel worker" due to
> administrator command
> FATAL: terminating background worker "parallel worker" due to
> administrator command
> FATAL: terminating background worker "parallel worker" due to
> administrator command
> FATAL: out of memory
> FATAL: out of memory
> ...
You are allowing over-committing memory, which in turn activates OOMK
(Out of Memory Killer) when the memory runs out. You have to restrict
the number of connections or parameters like work_mem and
hash_mem_multiplier. There is also a good article on Squishy Data:
https://www.crunchydata.com/blog/deep-postgresql-thoughts-the-linux-assassin
Basically, you should start with vm.overcommit_memory = 2
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2022-09-07 00:41:48 | Re: PostgreSQL Out of Memory |
| Previous Message | liam saffioti | 2022-09-05 11:54:56 | PostgreSQL Out of Memory |