You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@datafusion.apache.org by "gabotechs (via GitHub)" <gi...@apache.org> on 2026/01/05 10:00:27 UTC

Re: [PR] Use arrow pool to fix memory over accounting in aggregations [datafusion]

gabotechs commented on PR #19501:
URL: https://github.com/apache/datafusion/pull/19501#issuecomment-3709742565

   Even if this PR looks great, I'd love to explore what would it take to get the memory tracking fundamentals very right from the beginning, and see if there's an opportunity to be in a situation where memory tracking is more automatic, and we do not need to deal with two different `MemoryPool` traits with overlapping intentions.
   
   Wrote a small comment about that here https://github.com/apache/arrow-rs/issues/8938#issuecomment-3709632585. What do you think?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org