Re: repeated out of shared memory error - not related to max_locks_per_transaction

From: Rui DeSousa <rui(at)crazybean(dot)net>
To: Alfonso Moscato <alfonso(dot)moscato(at)merqurio(dot)it>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: repeated out of shared memory error - not related to max_locks_per_transaction
Date: 2018-07-20 15:02:31
Message-ID: CCDE87EE-29BF-4118-8C6F-5175D0DFD7C3@crazybean.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


Alfonso,

Do you happened to know how large the process is when it starts giving error messages, anywhere near 47GB?

— but we tried with work_mem to 130mb, shared_buffer to a maximum fo 40gb,

Having shared_buffer to 40GB would be two high for the current configuration and I would expect to see out of memory errors given that your system commit limit is 47GB; However, with shared_buffers at 23GB I don’t think you should be hitting the 47GB limit — are you?

To increase the commit limit you can add more swap and/or adjust the overcommit ratio.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2018-07-20 15:06:35 Re: R: repeated out of shared memory error - not related to max_locks_per_transaction
Previous Message Shreeyansh Dba 2018-07-20 14:57:23 Re: repeated out of shared memory error - not related to max_locks_per_transaction