From: "Alfonso Moscato" <alfonso.moscato@merqurio.it>
To: <066ce286@free.fr>
Cc: <pgsql-admin@lists.postgresql.org>
References: <00f101d42026$a32e17a0$e98a46e0$@merqurio.it>
 <1792205563.130550319.1532091999599.JavaMail.root@zimbra82-e14.priv.proxad.net>
In-Reply-To: 
 <1792205563.130550319.1532091999599.JavaMail.root@zimbra82-e14.priv.proxad.net>
Subject: R: R: repeated out of shared memory error - not related to
 max_locks_per_transaction
Date: Fri, 20 Jul 2018 15:10:19 +0200
Message-ID: <011e01d4202b$029ca590$07d5f0b0$@merqurio.it>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQHaHNKK2RzvnlT3g/SBW/kZdDISY6SMG87Q
Content-Language: it
Precedence: bulk

autovacuum_max_workers =3D 3
max_prepared_transactions =3D 0
block_size =3D 8192
wal_block_size =3D 8192

-----Messaggio originale-----
Da: 066ce286@free.fr <066ce286@free.fr>=20
Inviato: venerd=C3=AC 20 luglio 2018 15:07
A: Alfonso Moscato <alfonso.moscato@merqurio.it>
Cc: pgsql-admin@lists.postgresql.org
Oggetto: Re: R: repeated out of shared memory error - not related to =
max_locks_per_transaction

What are your values for :

autovacuum_max_workers
max_prepared_transactions
block_size
wal_block_size

?

----- Mail original -----
De: "Alfonso Moscato" <alfonso.moscato@merqurio.it>
=C3=80: "MichaelDBA" <MichaelDBA@sqlexec.com>, "Lance' 'Campbell" =
<lance@illinois.edu>
Cc: pgsql-admin@lists.postgresql.org
Envoy=C3=A9: Vendredi 20 Juillet 2018 14:39:01
Objet: R: repeated out of shared memory error - not related to =
max_locks_per_transaction


I thought it could have be.=20

Work_mem was 131mb and I reduced it to 60mb. Errors keep starting after =
one day and half.=20

Regards=20

alfonso=20


Da: MichaelDBA <MichaelDBA@sqlexec.com>=20
Inviato: venerd=C3=AC 20 luglio 2018 14:36=20
A: Campbell, Lance <lance@illinois.edu>=20
Cc: Alfonso Moscato <alfonso.moscato@merqurio.it>; =
pgsql-admin@lists.postgresql.org=20
Oggetto: Re: repeated out of shared memory error - not related to =
max_locks_per_transaction=20


Perhaps your "work_mem" setting is causing the memory problems. Try =
reducing it to see if that alleviates the problem.=20

Regards,=20
Michael Vitale=20


Campbell, Lance=20

Friday, July 20, 2018 8:32 AM=20


I would also lookup the definition of shared buffers and effective =
cache. If I remember correctly you can think of shared buffers as how =
much memory total PostgreSQL has to work with. Effective cache is how =
much memory is available for PostgreSQL to run, shared buffers, as well =
as an estimate of how much memory is available to the OS to cache files =
in memory. So effective cache should be equal to or larger than shared =
buffers. Effective cache is used to help with the SQL planning.=20

Double check the documentation.=20

Lance=20

Sent from my iPad=20