Postgres Pro
Downloads
Home   >   mailing lists

R: repeated out of shared memory error - not related to max_locks_per_transaction - Mailing list pgsql-admin

From Alfonso Moscato
Subject R: repeated out of shared memory error - not related to max_locks_per_transaction
Date
Msg-id 00f101d42026$a32e17a0$e98a46e0$@merqurio.it
Whole thread Raw
In response to Re: repeated out of shared memory error - not related to max_locks_per_transaction  (MichaelDBA <MichaelDBA@sqlexec.com>)
Responses Re: R: repeated out of shared memory error - not related to max_locks_per_transaction  (MichaelDBA <MichaelDBA@sqlexec.com>)
Re: R: repeated out of shared memory error - not related tomax_locks_per_transaction  (066ce286@free.fr)
List pgsql-admin
Tree view

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


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

 

 

pgsql-admin by date:

Previous
From: "Alfonso Moscato"
Date:
Subject: R: repeated out of shared memory error - not related to max_locks_per_transaction
Next
From: MichaelDBA
Date:
Subject: Re: R: repeated out of shared memory error - not related to max_locks_per_transaction