| From: | Uwe <uwe(at)oss4u(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, mark <pgroad(at)163(dot)com> |
| Subject: | Re: postgresql 9.5 has ocuuered OOM |
| Date: | 2017-12-20 17:01:40 |
| Message-ID: | 8602969.9kyGVsOKG8@tiburon |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday, December 20, 2017 9:59:24 AM PST David G. Johnston wrote:
> On Wed, Dec 20, 2017 at 9:44 AM, Uwe <uwe(at)oss4u(dot)com> wrote:
> > IIRC work_mem is a PER CONNECTION setting,
>
> The docs for this setting clearly state that a single connection/session
> can itself use multiple times this values for a single query.
>
> https://www.postgresql.org/docs/10/static/runtime-config-resource.html#RUNTI
> ME-CONFIG-RESOURCE-MEMORY
>
So even worse for the OP. No wonder he runs out of memory.
Thanks for the correction.
Uwe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rakesh Kumar | 2017-12-20 17:09:56 | Caching of sproc |
| Previous Message | David G. Johnston | 2017-12-20 16:59:24 | Re: postgresql 9.5 has ocuuered OOM |