Re: Parallel Seq Scan
От | Robert Haas |
---|---|
Тема | Re: Parallel Seq Scan |
Дата | |
Msg-id | CA+TgmobUN8N0-WD6HgopcTTsyM+kesK_r9Sre6k1+vA_pkhkTg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Parallel Seq Scan (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: Parallel Seq Scan
|
Список | pgsql-hackers |
On Sun, Nov 15, 2015 at 1:12 AM, Amit Kapila <amit.kapila16@gmail.com> wrote: > Thanks for the report. > > 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. Oops. Committed. > Another thing I have noticed is that we need to build the remap info > target list contains record type of attrs, so ideally it should not even go > in > this path when such attrs are not present. The reason for the same was > that the tuple descriptor stored in TQueueDestReceiver was not updated, > attached patch fix_initialization_tdesc_v1 fixes this issue. I don't understand this part. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: