Re: ERROR: too many dynamic shared memory segments
От | Dilip Kumar |
---|---|
Тема | Re: ERROR: too many dynamic shared memory segments |
Дата | |
Msg-id | CAFiTN-u7j1QSqaa54qJiA8o2C+21YMy6kgFk-TaaiFgLjU234A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ERROR: too many dynamic shared memory segments (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: ERROR: too many dynamic shared memory segments
Re: ERROR: too many dynamic shared memory segments |
Список | pgsql-general |
On Tue, Nov 28, 2017 at 7:13 PM, Robert Haas wrote:
> On Tue, Nov 28, 2017 at 2:32 AM, Dilip Kumar
> 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
В списке pgsql-general по дате отправления: