autovacuum_max_workers = 3
max_prepared_transactions = 0
block_size = 8192
wal_block_size = 8192
-----Messaggio originale-----
Da: 066ce286@free.fr <066ce286@free.fr>
Inviato: venerdì 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>
À: "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
sharedbuffers as how much memory total PostgreSQL has to work with. Effective cache is how much memory is available for
PostgreSQLto 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
SQLplanning.
Double check the documentation.
Lance
Sent from my iPad
