Postgres Pro
Downloads
Home   >   mailing lists

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

From MichaelDBA
Subject Re: repeated out of shared memory error - not related to max_locks_per_transaction
Date
Msg-id 5B51D72B.3040204@sqlexec.com
Whole thread Raw
In response to Re: repeated out of shared memory error - not related tomax_locks_per_transaction  ("Campbell, Lance" <lance@illinois.edu>)
Responses R: repeated out of shared memory error - not related to max_locks_per_transaction  ("Alfonso Moscato" <alfonso.moscato@merqurio.it>)
Re: repeated out of shared memory error - not related tomax_locks_per_transaction  (Fabio Pardi <f.pardi@portavita.eu>)
List pgsql-admin
Tree view
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: "Campbell, Lance"
Date:
Subject: Re: repeated out of shared memory error - not related tomax_locks_per_transaction
Next
From: "Alfonso Moscato"
Date:
Subject: R: repeated out of shared memory error - not related to max_locks_per_transaction