Re: Parallel Seq Scan
От | Amit Kapila |
---|---|
Тема | Re: Parallel Seq Scan |
Дата | |
Msg-id | CAA4eK1KcY3d1MQcQK6y5u=KUNtP2Vvywy4RCQ8zEC8Vx33XTLw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Parallel Seq Scan (Jeff Janes <jeff.janes@gmail.com>) |
Список | pgsql-hackers |
On Mon, Nov 16, 2015 at 10:36 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
>
> On Sat, Nov 14, 2015 at 10:12 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> > On Fri, Nov 13, 2015 at 11:05 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> >
> > I think main reason of the leak in workers seems to be due the reason
> > that one of the buffer used while sending tuples (in function
> > BuildRemapInfo)
> > from worker to master is not getting freed and it is allocated for each
> > tuple worker sends back to master. I couldn't find use of such a buffer,
> > so I think we can avoid the allocation of same or atleast we need to free
> > it. Attached patch remove_unused_buf_allocation_v1.patch should fix the
> > issue.
>
> Thanks, that patch (as committed) has fixed the problem for me.
>
>
> On Sat, Nov 14, 2015 at 10:12 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> > On Fri, Nov 13, 2015 at 11:05 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> >
> > I think main reason of the leak in workers seems to be due the reason
> > that one of the buffer used while sending tuples (in function
> > BuildRemapInfo)
> > from worker to master is not getting freed and it is allocated for each
> > tuple worker sends back to master. I couldn't find use of such a buffer,
> > so I think we can avoid the allocation of same or atleast we need to free
> > it. Attached patch remove_unused_buf_allocation_v1.patch should fix the
> > issue.
>
> Thanks, that patch (as committed) has fixed the problem for me.
>
Thanks to you as well for verification.
В списке pgsql-hackers по дате отправления: