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

From: "Alfonso Moscato" <alfonso(dot)moscato(at)merqurio(dot)it>
To: "'Rui DeSousa'" <rui(at)crazybean(dot)net>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: R: repeated out of shared memory error - not related to max_locks_per_transaction
Date: 2018-07-20 15:38:40
Message-ID: 019a01d4203f$bc4983f0$34dc8bd0$@merqurio.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi Rui,
we have 100 forked postgres processes, I don't know how to determine if we are hitting the 47Gb limit.
Any suggestion?

-----Messaggio originale-----
Da: Rui DeSousa <rui(at)crazybean(dot)net>
Inviato: venerdì 20 luglio 2018 17:03
A: 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
Oggetto: Re: repeated out of shared memory error - not related to max_locks_per_transaction

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 Alfonso Moscato 2018-07-20 15:40:32 R: repeated out of shared memory error - not related to max_locks_per_transaction
Previous Message Alfonso Moscato 2018-07-20 15:30:54 R: repeated out of shared memory error - not related to max_locks_per_transaction