R: repeated out of shared memory error - not related to max_locks_per_transaction - Mailing list pgsql-admin

From Alfonso Moscato
Subject R: repeated out of shared memory error - not related to max_locks_per_transaction
Date
Msg-id 019a01d4203f$bc4983f0$34dc8bd0$@merqurio.it
Whole thread Raw
In response to Re: repeated out of shared memory error - not related tomax_locks_per_transaction  (Rui DeSousa <rui@crazybean.net>)
Responses Re: repeated out of shared memory error - not related tomax_locks_per_transaction  (Rui DeSousa <rui@crazybean.net>)
List 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@crazybean.net>
Inviato: venerdì 20 luglio 2018 17:03
A: Alfonso Moscato <alfonso.moscato@merqurio.it>
Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-admin@lists.postgresql.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
errorsgiven that your system commit limit is 47GB; However, with shared_buffers at 23GB I don’t think you should be
hittingthe 47GB limit — are you? 

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







pgsql-admin by date:

Previous
From: "Alfonso Moscato"
Date:
Subject: R: repeated out of shared memory error - not related to max_locks_per_transaction
Next
From: "Alfonso Moscato"
Date:
Subject: R: repeated out of shared memory error - not related to max_locks_per_transaction