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

I took the setting from pgtune:

https://pgtune.leopard.in.ua/#/

Anyway, I will try to further reduce it.

It is high because we have a very complex database, queries with a lot of tables, and million of records.

Furthermore, I see a lot of free memory.

Try reducing it further just to make sure.

Alfonso Moscato

Friday, July 20, 2018 8:39 AM

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

 

MichaelDBA

Friday, July 20, 2018 8:35 AM

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