| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Nicola Contu <nicola(dot)contu(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Alessandro Aste <Alessandro(dot)aste(at)gtt(dot)net> |
| Subject: | Re: ERROR: too many dynamic shared memory segments |
| Date: | 2020-02-01 03:08:39 |
| Message-ID: | CA+hUKGLyxv6+5WeMcg3+UC2HX4rtoWGzgnsx+Sfv++MJwEi-WQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jan 31, 2020 at 11:05 PM Nicola Contu <nicola(dot)contu(at)gmail(dot)com> wrote:
> Do you still recommend to increase max_conn?
Yes, as a workaround of last resort. The best thing would be to
figure out why you are hitting the segment limit, and see if there is
something we could tune to fix that. If you EXPLAIN your queries, do
you see plans that have a lot of "Gather" nodes in them, perhaps
involving many partitions? Or are you running a lot of parallel
queries at the same time? Or are you running queries that do very,
very large parallel hash joins? Or something else?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2020-02-01 10:21:33 | Re: Need support on tuning at the time of index creation |
| Previous Message | Thomas Munro | 2020-02-01 03:00:56 | Re: ERROR: too many dynamic shared memory segments |