From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Jakub Glapa <jakub(dot)glapa(at)gmail(dot)com>, Forums postgresql <pgsql-general(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ERROR: too many dynamic shared memory segments |
Date: | 2017-11-28 14:45:09 |
Message-ID: | CAFiTN-u7j1QSqaa54qJiA8o2C+21YMy6kgFk-TaaiFgLjU234A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Tue, Nov 28, 2017 at 7:13 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Nov 28, 2017 at 2:32 AM, Dilip Kumar <dilipbalaut(at)gmail(dot)com>
> wrote:
> > I think BitmapHeapScan check whether dsa is valid or not if DSA is not
> > valid then it should assume it's non-parallel plan.
> >
> > Attached patch should fix the issue.
>
> So, create the pstate and then pretend we didn't? Why not just avoid
> creating it in the first place, like this?
>
This is better way to fix it.
>
> I haven't checked whether this fixes the bug, but if it does, we can
> avoid introducing an extra branch in BitmapHeapNext.
With my test it's fixing the problem.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Henrik Uggla | 2017-11-28 14:48:12 | SV: Refreshing materialized views |
Previous Message | Tom Lane | 2017-11-28 14:35:33 | Re: Plan for update ... where a is not distinct from b |
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2017-11-28 14:52:09 | Re: [PATCH] Atomic pgrename on Windows |
Previous Message | Aleksander Alekseev | 2017-11-28 14:39:16 | Re: new function for tsquery creartion |