pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alfonso Moscato <alfonso.moscato@merqurio.it>
To: 'MichaelDBA' <MichaelDBA@sqlexec.com>
To: 'Campbell, Lance' <lance@illinois.edu>
Cc: pgsql-admin@lists.postgresql.org
Subject: R: repeated out of shared memory error - not related to max_locks_per_transaction
Date: Fri, 20 Jul 2018 14:39:01 +0200
Message-ID: <00f101d42026$a32e17a0$e98a46e0$@merqurio.it> (raw)
In-Reply-To: <5B51D72B.3040204@sqlexec.com>
References: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it>
	<C6379276-7F3F-4C53-AD89-BEB59B430169@illinois.edu>
	<5B51D72B.3040204@sqlexec.com>

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 <mailto:lance@illinois.edu> 

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: <00f101d42026$a32e17a0$e98a46e0$@merqurio.it>
Permalink:  ../00f101d42026$a32e17a0$e98a46e0$@merqurio.it/
Also on:    postgresql.org/message-id/00f101d42026$a32e17a0$e98a46e0$@merqurio.it

 · 

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: alfonso.moscato@merqurio.it, MichaelDBA@sqlexec.com, lance@illinois.edu, pgsql-admin@lists.postgresql.org
  Subject: Re: R: repeated out of shared memory error - not related to max_locks_per_transaction
  In-Reply-To: <00f101d42026$a32e17a0$e98a46e0$@merqurio.it>

* 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