New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak in ao_truncate_replay #11202
Comments
Agree @hidva wish to open PR to fix it? |
Ok
|
hidva
added a commit
to hidva/gpdb
that referenced
this issue
Nov 25, 2020
The value returned by GetDatabasePath is palloc'd, and CurrentMemoryContext is TopMemoryContext when we enter ao_truncate_replay(), so we should do a pfree. Fix greenplum-db#11202
kainwen-zz
pushed a commit
that referenced
this issue
Nov 25, 2020
The value returned by GetDatabasePath is palloc'd, and CurrentMemoryContext is TopMemoryContext when we enter ao_truncate_replay(), so we should do a pfree. Fix Github issue 11202 (#11202)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Greenplum version or build
Step to reproduce the behavior
ddl.sql.txt
insert.sql.txt
Root cause
It seems we should do
pfree(dbPath)
in ao_truncate_replay().There is no invocation of
pfree()
, and theCurrentMemoryContext
isTopMemoryContext
The text was updated successfully, but these errors were encountered: