| From: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
|---|---|
| To: | "Campbell, Lance" <lance(at)illinois(dot)edu> |
| Cc: | Alfonso Moscato <alfonso(dot)moscato(at)merqurio(dot)it>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: repeated out of shared memory error - not related to max_locks_per_transaction |
| Date: | 2018-07-20 12:35:55 |
| Message-ID: | 5B51D72B.3040204@sqlexec.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
> Campbell, Lance <mailto:lance(at)illinois(dot)edu>
> 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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alfonso Moscato | 2018-07-20 12:37:21 | R: repeated out of shared memory error - not related to max_locks_per_transaction |
| Previous Message | Campbell, Lance | 2018-07-20 12:32:53 | Re: repeated out of shared memory error - not related to max_locks_per_transaction |