Re: [report] memory leaks in COPY FROM on partitioned table
От | Amit Langote |
---|---|
Тема | Re: [report] memory leaks in COPY FROM on partitioned table |
Дата | |
Msg-id | c765b9b3-f912-f2af-bdd6-cb5e142dbf04@lab.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: [report] memory leaks in COPY FROM on partitioned table (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: [report] memory leaks in COPY FROM on partitioned table
|
Список | pgsql-hackers |
On 2018/08/02 6:03, Alvaro Herrera wrote: > On 2018-Aug-01, Andres Freund wrote: > >> On 2018-08-01 16:38:11 -0400, Alvaro Herrera wrote: >>> On 2018-Jul-24, Amit Langote wrote: >>> >>>> Your patch takes care of allocation happening inside >>>> get_partition_for_tuple, but as you mention there might be others in its >>>> caller ExecFindPartition. So, I think we should switch to the per-tuple >>>> context in ExecFindPartition. >>> >>> Right, makes sense. Pushed that way. >> >> The buildfarm does not like this one: >> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=desmoxytes&dt=2018-08-01%2020%3A40%3A02 >> (and a lot of other reports from my animals) > > Hmm, variable shadowing ... Crap, sorry about forgetting to remove that and thanks for taking care of that. Thanks, Amit
В списке pgsql-hackers по дате отправления: