datbth opened a new issue, #43791:
URL: https://github.com/apache/arrow/issues/43791
### Describe the usage question you have. Please include as many useful
details as possible.
I'm trying to understand Arrow memory management in order to do it properly
when using Arrow in Go.
I found this issue #35232, but I still don't really get it.
Here are some example questions:
1. It was stated in the above issue that when using the default Go
allocator, we "don't actually have to call `Retain`/`Release`", but
* Would calling `Retain`/`Release` properly help Go GC do its job more
timely/accurately?
* Would calling `Retain`/`Release` wrongly make Go GC perform worse or
even lead to bugs?
2. If I want to call `Retain`/`Release` properly, how should I do it? How
can I know if an Arrow Record returned by an Arrow library function (or any
third-party library function) is already `Retain`ed or not?
Thank you for looking into this.
### Component(s)
Go
--
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: issues-unsubscr...@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
