Re: repeated out of shared memory error - not related to max_locks_per_transaction
| От | MichaelDBA |
|---|---|
| Тема | Re: repeated out of shared memory error - not related to max_locks_per_transaction |
| Дата | |
| Msg-id | 5B51D72B.3040204@sqlexec.com обсуждение исходный текст |
| Ответ на | Re: repeated out of shared memory error - not related tomax_locks_per_transaction ("Campbell, Lance" <lance@illinois.edu>) |
| Ответы |
R: repeated out of shared memory error - not related to max_locks_per_transaction
Re: repeated out of shared memory error - not related tomax_locks_per_transaction |
| Список | pgsql-admin |
Perhaps your "work_mem" setting is causing the memory problems. Try reducing it to see if that alleviates the problem.
Regards,
Michael Vitale
Regards,
Michael Vitale
Friday, July 20, 2018 8:32 AMI 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 по дате отправления: