pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: 066ce286@free.fr
To: Alfonso Moscato <alfonso.moscato@merqurio.it>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: R: repeated out of shared memory error - not related to max_locks_per_transaction
Date: Fri, 20 Jul 2018 15:06:39 +0200 (CEST)
Message-ID: <1792205563.130550319.1532091999599.JavaMail.root@zimbra82-e14.priv.proxad.net> (raw)
In-Reply-To: <00f101d42026$a32e17a0$e98a46e0$@merqurio.it>

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>
À: "MichaelDBA" <MichaelDBA@sqlexec.com>, "Lance' 'Campbell" <lance@illinois.edu>
Cc: pgsql-admin@lists.postgresql.org
Envoyé: 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. 

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

Regards 

alfonso 





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



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

Regards, 
Michael Vitale 









Campbell, Lance 

Friday, July 20, 2018 8:32 AM 



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. 

Double check the documentation. 

Lance 

Sent from my iPad 








view thread (16+ messages)  latest in thread

Message-ID: <1792205563.130550319.1532091999599.JavaMail.root@zimbra82-e14.priv.proxad.net>
Permalink:  ../1792205563.130550319.1532091999599.JavaMail.root@zimbra82-e14.priv.proxad.net/
Also on:    postgresql.org/message-id/1792205563.130550319.1532091999599.JavaMail.root@zimbra82-e14.priv.proxad.net

 · 

reply

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: 066ce286@free.fr, alfonso.moscato@merqurio.it, pgsql-admin@lists.postgresql.org
  Subject: Re: R: repeated out of shared memory error - not related to max_locks_per_transaction
  In-Reply-To: <1792205563.130550319.1532091999599.JavaMail.root@zimbra82-e14.priv.proxad.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