Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.17\))
Subject: Re: repeated out of shared memory error - not related to
 max_locks_per_transaction
From: Rui DeSousa <rui@crazybean.net>
In-Reply-To: <018201d42038$7146a6a0$53d3f3e0$@merqurio.it>
Date: Fri, 20 Jul 2018 11:02:31 -0400
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
 pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <CCDE87EE-29BF-4118-8C6F-5175D0DFD7C3@crazybean.net>
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>
To: Alfonso Moscato <alfonso.moscato@merqurio.it>
Precedence: bulk


Alfonso,

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

=E2=80=94 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=E2=80=99t think you should be hitting the 47GB limit =E2=80=94 are =
you?

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


=20