From: Rui DeSousa <rui@crazybean.net>
To: Alfonso Moscato <alfonso.moscato@merqurio.it>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: repeated out of shared memory error - not related to max_locks_per_transaction
Date: Fri, 20 Jul 2018 11:02:31 -0400
Message-ID: <CCDE87EE-29BF-4118-8C6F-5175D0DFD7C3@crazybean.net> (raw)
In-Reply-To: <018201d42038$7146a6a0$53d3f3e0$@merqurio.it>
References: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it>
<17662.1532096551@sss.pgh.pa.us>
<016801d42037$4f5d4630$ee17d290$@merqurio.it>
<E94C6526-93DF-44CC-BCF6-11AC1CAEAAD0@crazybean.net>
<018201d42038$7146a6a0$53d3f3e0$@merqurio.it>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rui@crazybean.net, alfonso.moscato@merqurio.it, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
Subject: Re: repeated out of shared memory error - not related to max_locks_per_transaction
In-Reply-To: <CCDE87EE-29BF-4118-8C6F-5175D0DFD7C3@crazybean.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox